Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Xxx.dbf did not match the entries in the database
Message
From
15/11/2007 23:03:08
 
 
To
15/11/2007 18:26:20
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01268968
Message ID:
01269342
Views:
5
>>>>I am creating a table in a database. this is the last one but I am getting the error "xxx.dbf did not match the entries in the database"
>>>>
>>>>I have never seen that error before and I have no clue what's causing it.
>>>>
>>>>I have 60 tables in the database and this table has 220 columns.
>>>>
>>>>I have a create script, very simple. the table get created but I get the error after I close the project and re-open it and try to browse or modify the table.
>>>>
>>>>Any idea
>>>>
>>>>Thanks
>>>
>>>Perhaps you have an improper fieldname?
>>>If the table can be opened, try
>>>
>>>copy to newtablename.dbf database yourdatabase
>>>
>>>Then delete the original and rename the new table to the old name using the project manager.
>>>Also, if the table is being created on a network, be sure to use a valid full network path in the filespec.
>>
>>Nope, nothing improper. Somehow VFP has an issue with table having many columns and long name. I was able to break the table into 3 tables using script.
>>
>>I think Marcia put their hand on the solution but it is ridiculous not to be able to create a table using script.
>
>I create tables with script all the time but not with this many fields. If your field names are constant you could use COPY STRUCTURE EXTENDED to create a fixed template and then CREATE FROM to build the table.
>
>Alternatively, you could build the "EXTENDED" table with script and then CREATE FROM to build your final table.
>
>OR, you could CREATE CURSOR and then COPY TO table.
>OR, create a smaller table and loop to add the additional fields one at a time. UGH!
>You can also build a table with a SELECT statement.
>If the long name is the problem, create it with a shorter name and then rename it.
>There are many ways to skin the cat.
>(Actually, I like cats. Never would want to skin one.)

Do you use long column name with your tables???
By the way, I am not getting the error until I have over 120 columns.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform