 | |
Suddenly no tables could be opened ...
comp.databases.paradox comp.databases.paradox
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: Suddenly no tables could be opened ... -
09-25-2008
, 10:35 AM
|
Assuming the data is on the server as it should be (not the workstations) then get the workstations out. Look for and delete any .lck and .net files in the data space and on the users working directories and priv directories. Tutility or chimney sweep the files to fix any damage. Check the idapi.cfg file to make sure it is intact and then make sure all users are pointed to the same .cfg file or copies that are exactly the same. Denn Santoro President Resource Development Associates http://www.RDAWorldWide.Com Offices in the United States and Germany Providing solutions to health care, business, governments and non-profits since 1982 Nils Gustaf Lindgren wrote: .... or rather, during the morning the small database distributed over two work stations from a server malfunctioned more and more. After claiming that indices were out of date, tables can no longer be opened and I get the error message "You have attempted to open a database that is in use by someone else, but the database cannot be shared. You must set the location for the .NET control file" Here is the setup: two workstations with XP Pro, connected through wire to a SBS Server. No connection to the Internet, and no update nor newly installed software. The server is not connected to Internet either, nor has it been updated for several months. The net drectory is the shared root on the server as it has been for more than a decade (OK we have changed servers). We run Pdx 9. I have never previously had any questions concerning "the .NET control file". Where do I start looking? Cheers Nils |
#22
| |||
| |||
|
|
Assuming the data is on the server as it should be (not the workstations) then get the workstations out. Look for and delete any .lck and .net files in the data space and on the users working directories and priv directories. Tutility or chimney sweep the files to fix any damage. Check the idapi.cfg file to make sure it is intact and then make sure all users are pointed to the same .cfg file or copies that are exactly the same. Denn Santoro President Resource Development Associates http://www.RDAWorldWide.Com Offices in the United States and Germany Providing solutions to health care, business, governments and non-profits since 1982 Nils Gustaf Lindgren wrote: .... or rather, during the morning the small database distributed over two work stations from a server malfunctioned more and more. After claiming that indices were out of date, tables can no longer be opened and I get the error message "You have attempted to open a database that is in use by someone else, but the database cannot be shared. You must set the location for the .NET control file" Here is the setup: two workstations with XP Pro, connected through wire to a SBS Server. No connection to the Internet, and no update nor newly installed software. The server is not connected to Internet either, nor has it been updated for several months. The net drectory is the shared root on the server as it has been for more than a decade (OK we have changed servers). We run Pdx 9. I have never previously had any questions concerning "the .NET control file". Where do I start looking? Cheers Nils |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.