Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Approach locking with paradox tables
- Thread starter cobweb
- Start date
Paradox files can be shared only if there is a "primary key" field defined. And there is information in the "Help" in Approach if you use the find tab and enter Paradox as the search argument.
One Lotus Tech note also has the following information:
The error message is known to occur if Paradox file sharing is not set up correctly, if the .DB file is corrupt, or if the system dates on the PC's trying to access the file are different. These situations are explained below, along with instructions on how to resolve the problem.
1. Paradox .DB Network File Sharing
Network file sharing of Paradox .DB files is controlled through the network control file PARADOX.NET. This file monitors concurrent uses of a .DB file on a network.
In order to share Paradox .DB files on a network, the Local Area Network (LAN) Administrator should make sure that the PARADOX.NET file is located in the proper directory.
To specify the location of the PARADOX.NET file:
a. Choose File, Open.
b. Highlight the name of the appropriate .DB file, then click Connect to display the Paradox Network Connection dialog box.
c. Enter a User Name and Network Control File Path for the
PARADOX.NET file, then click OK.
NOTE: Enter only the pathname, not the filename.
d. Close Approach, then reopen it.
BACKGROUND INFORMATION: If the location of the PARADOX.NET file is not specified, the file will open on the network as a single user file. When a Paradox database is opened on a network, Approach verifies the location of the PARADOX.NET in your APPROACH.INI file. (.INI files are no longer used in the 9.x versions of Approach)
2. Paradox .DB File Is Damaged
The .DB file became damaged during a system crash. The damage occurred as a result of trying to execute a Find operation.
The problem can be resolved by opening a previously saved version of the .DB file and exporting it to a new .DB file.
3. System Dates On The Computers Differ
The error message will also occur if the System Date is not set properly on the computers trying to access the .DB file. In one case, the system date on one PC was one day ahead of the date on the second PC trying to access the .DB file.
Setting the system date on both PC's to the same date resolved the problem in this case.
One Lotus Tech note also has the following information:
The error message is known to occur if Paradox file sharing is not set up correctly, if the .DB file is corrupt, or if the system dates on the PC's trying to access the file are different. These situations are explained below, along with instructions on how to resolve the problem.
1. Paradox .DB Network File Sharing
Network file sharing of Paradox .DB files is controlled through the network control file PARADOX.NET. This file monitors concurrent uses of a .DB file on a network.
In order to share Paradox .DB files on a network, the Local Area Network (LAN) Administrator should make sure that the PARADOX.NET file is located in the proper directory.
To specify the location of the PARADOX.NET file:
a. Choose File, Open.
b. Highlight the name of the appropriate .DB file, then click Connect to display the Paradox Network Connection dialog box.
c. Enter a User Name and Network Control File Path for the
PARADOX.NET file, then click OK.
NOTE: Enter only the pathname, not the filename.
d. Close Approach, then reopen it.
BACKGROUND INFORMATION: If the location of the PARADOX.NET file is not specified, the file will open on the network as a single user file. When a Paradox database is opened on a network, Approach verifies the location of the PARADOX.NET in your APPROACH.INI file. (.INI files are no longer used in the 9.x versions of Approach)
2. Paradox .DB File Is Damaged
The .DB file became damaged during a system crash. The damage occurred as a result of trying to execute a Find operation.
The problem can be resolved by opening a previously saved version of the .DB file and exporting it to a new .DB file.
3. System Dates On The Computers Differ
The error message will also occur if the System Date is not set properly on the computers trying to access the .DB file. In one case, the system date on one PC was one day ahead of the date on the second PC trying to access the .DB file.
Setting the system date on both PC's to the same date resolved the problem in this case.
- Status
Similar threads
- Locked
- Question