Tables are read only after recovery

[dentarthurdent]

I have a very old database application, originally installed on a windows 3.11 machine, using the Paradox 7 runtime files. The app was initially installed in around 1995 , long before I was involved. I have no installation disks for the application and the company who wrote it no longer exist.
The original machine has now failed and I just had time to move the program and data folders onto another PC.
I installed BDE ver 2.52 (to match old PC) and after a bit of trial and error got the app to run. I can view all the records fine and print all the reports but I can't edit the data. When I try to edit, the app tells me the table is read only. The app is password protected but I have the password the user claims is the one which he has always used with no problems.
Is there any way to remove the security (if indeed that is what the problem is) on the tables?

Will.

 

[Langley]

If you saved them to a CD and then back, then make sure that you changed the file properties from Read Only.

Otherwise, the password you have is a level that does does not permit editing. The security is not that tough to crack and there are some resources on the Internet that can help you.



Mac

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us

 

[dentarthurdent]

Thanks Mac,
The entire data folder has a read only attribute. When I remove the attribute, it reappears immediately. I have checked the inherited permissions (NTFS) and have given 'everyone' 'full control' of the folder and subfolders. Even then when I remove the read only attribute it reappears.
I guess this is what is stopping me from editing the tables but how do I get rid of the 'read only' attribute?
You mention resources on the net that can crack the file security - I used passware to crack the password but it still only allows me read access. Is there anywhere I can go to just remove the security completely?

Thanks,
Will.

 

[Langley]

I'm guessing that you are using XP. Log in as the administrator and you should be able to change the attribute. Paradox password security has nothing to do with the problem.

Hope this helps,

Mac


Mac

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us

 

[dentarthurdent]

I've tried everything I can think of to remove the protection on the tables, with no success. I even moved the whole application onto a purpose built Windows 3.11 machine with a FAT filesystem and the tables were still read only.
I think the only option is to re-write the app in access and manually transfer the data. It's not a complex app and the data volume is small. I suppose it's about time I modified the database anyway as needs have changed somewhat.
Thanks for your time anyway Mac.

Regards,
Will.

 

[footpad]

Will,

That's *very* strange. In most cases I've seen, clearing the read-only attribute solves the problem.

You might also make sure that everyone's out of the aplication and then see if there are stray *.LCK files in the data directory. That may also help.

Hope this does...

-- Lance