 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
George Guest
|
Posted: Mon Jan 12, 2004 3:02 pm Post subject: Paradox BDE runtime config files |
|
|
Can anybody tell me what mechanism the BDE uses to keep track of table
states?
I have an app that will no longer run because it tells me a table has tried
an operation that cannot be performed on a closed dataset. The dataset
concerned is set to active etc in the code but the app will not see it.
I have rebooted, replaced the data tables and rebuilt the app - no change.
Is there some sort of config or lock file I need to get rid of?
Many thanks in anticipation.
George
|
|
| Back to top |
|
 |
Dwayne Guest
|
Posted: Sun Jan 18, 2004 7:01 pm Post subject: Re: Paradox BDE runtime config files |
|
|
| Quote: | I have an app that will no longer run because it tells me a table has
tried an operation that cannot be performed on a closed dataset. |
a. Make sure the table actually exists in the proper directory. (not
test directory)
b. Make sure that the Table is being opened in the first place.... Do
this easily by creating a DBGrid, activating it at runtime, and running your
program... If data exists in the grid, you *know* the file is open. (or you
can look at your data of that file.
c. Make sure your program has Active set as true.
d. If a,b, & c are true, then you definitely have problems.
I suspect a couple things in happening....
a. Your table is corrupt, and it is not getting opened correctly.
Thus the table is inactive and you are attempting to read/write to a
inactive table.
b. Table Active is not set to true.
c. Improper location/name of table.
d. Is your program setting the Table Active to false someplace?
e. Are you using the correct Table type for the reading/writing
the file? Don't use ASCII or DBASE for Paradox or something like that. I
usually set this on "Default"
Try this (after saving a backup of your files!!!) open your BCB, go
to the table and Right Click on that table. Click on Update Table
definitions.
Then run your program and CREATE a new table from your updated
Table definitions. (It will be a Paradox Level 7 with the ending of .db).
Find out "Where" this file is being created. and find out "What
fields are being created". and attempt to access this file via your program.
See if the same error exists.
If the error does not exist, this may give you a clue to what is happening.
Dwayne
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|