i104 FILE OPEN

[Guest_imported]

Hi,

This problem is driving me nuts. Whilst doing a restructure, a single .db table (with nothing else associated with it) has become 'corrupt'. It crashes out with a message saying I104 File Open. When I try and view the blank table it takes about 10 seconds to open. I have tried tutility, it worked fine (but did take along time). I've tried copying the table but a message comes up saying the tables has no records and is write protected (it is not in Paradox or the Network). I deleted the table and manually recreated it. Same effect!!???????

 

[PhilUK]

We have had 50 or so occurances in 3 years where Paradox has given the message
"Assignment not permitted for write-protected table" or
tablename "is write-protected and can't be modified"

We don't do this anywhere in the code, so it is coming from somewhere. I never did track the problem down, since it cleared itself each time.

I have also had problems with small, slow to open tables, on Win98 PC to Novell Network. The tables were ok when re-created from a test copy. This become worse when our server was optimised for 32 bit apps and the Bindary was no longer used.

All in, I think there is something low level going on.

Sorry, I can't give any specifics, hope things get cleared.

Phil