How Many fields can have a Dbf ?
In portuguese:
Usando o FoxBase 2.5, só permite criar 128 campos com 255 caracteres cada um. Via DBCREATE() do xHarbour, talvez uns 400 Campos, mas o FoxBase não abrirá. Melhor escolha é criar vários *.DBFs e dividir as tarefas entre eles.
In Español:
Usando FoxBase 2.5, solo le permite crear 128 campos con 255 caracteres cada uno. A través de DBCREATE () de xHarbour, tal vez 400 campos, pero FoxBase no se abre. La mejor opción es crear varios * .DBF y dividir las tareas entre ellos.
In English:
Using FoxBase 2.5, it only allows you to create 128 fields with 255 characters each. Via DBCREATE() from xHarbour, maybe 400 Fields, but FoxBase won't open. Best choice is to create multiple *.DBFs and split tasks among them.
I think We use Harbour and Fivewin, So No Foxbase
Hi,
I think DBF is not the future .
It is safer to use SQL with Access or MySQL or MS SQL
SQL is very very faster than DBF .
Have a good day ,
Philippe from Belgium
Hi Silvio,
May I ask what you store in your fields.
For example, I use one field to store if a guest has been in the hotel in the different years.
I use a character field and I insert:
"JNNJNJNNNJJJ"
The first chatacter is for the year 2010, the second for 2011, ...
J means he was a guest, N not.
This reduces the number of fields inside the database.
Best regards,
Otto
Otto wrote:Hi Silvio,
May I ask what you store in your fields.
For example, I use one field to store if a guest has been in the hotel in the different years.
I use a character field and I insert:
"JNNJNJNNNJJJ"
The first chatacter is for the year 2010, the second for 2011, ...
J means he was a guest, N not.
This reduces the number of fields inside the database.
Best regards,
Otto
Silvio,
That sounds doable if you use multiple DBFs that are linked.
For example:
An exercise description file
A student file ( one record for each student )
A daily exercise record ( it can have a link to the description, and one to the student, plus fields for date and results )
Your program then displays the data based on your selection criterion. To load the data each day, create an array. The first element can be the student name, and then the additional elements can be for the exercises they do that day. Using the student file, you create a two dimensional array, with one for each student. Then use an xbrowse, editable, to show the array. The user sees it and can fill in the values. When you save it, upon completion, the array elements are recorded in appended daily records for each student.
Views and reports can then be created to see the data, and you can even build a routine to edit it when desirable.
Tim
TimStone wrote:Silvio,
That sounds doable if you use multiple DBFs that are linked.
For example:
An exercise description file
A student file ( one record for each student )
A daily exercise record ( it can have a link to the description, and one to the student, plus fields for date and results )
Your program then displays the data based on your selection criterion. To load the data each day, create an array. The first element can be the student name, and then the additional elements can be for the exercises they do that day. Using the student file, you create a two dimensional array, with one for each student. Then use an xbrowse, editable, to show the array. The user sees it and can fill in the values. When you save it, upon completion, the array elements are recorded in appended daily records for each student.
Views and reports can then be created to see the data, and you can even build a routine to edit it when desirable.
Tim
