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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PARADOX "TRAPPING" USERS 1
- Thread starter Hpatel
- Start date
-
1
- #2
- Thread starter
- #3
Try this first:
Have you had all users exist Pdox and delete the Pdoxusrs.net file?
If that doesn't fix the problem… Well, I guess we'll have to do the hard way.
Let's start with the basic.
Which version of paradox?
On what type of network? Windows NT?
How are user accessing the tables?
Using forms?
or
Just plain table?
How long has this been going on?
Has anyone made any changes to the network or application before these problem surfaces?
When you say "log in", what do you mean by it?
Are users have to enter user id and password to gain access to the data?
Not to confuse with normal network log-in procedures.
When the user is in the database, can the user make changes to the data?
If so, were the data saved when user left the database?
Are there multiple versions of Pdox running?
Have you had all users exist Pdox and delete the Pdoxusrs.net file?
If that doesn't fix the problem… Well, I guess we'll have to do the hard way.
Let's start with the basic.
Which version of paradox?
On what type of network? Windows NT?
How are user accessing the tables?
Using forms?
or
Just plain table?
How long has this been going on?
Has anyone made any changes to the network or application before these problem surfaces?
When you say "log in", what do you mean by it?
Are users have to enter user id and password to gain access to the data?
Not to confuse with normal network log-in procedures.
When the user is in the database, can the user make changes to the data?
If so, were the data saved when user left the database?
Are there multiple versions of Pdox running?
- Thread starter
- #5
Hi Joe,
What does deleting the Pdoxusrs.net file does? Also, i am not familiar with the TUtility that does data corruption check? Is these a program? and where can i find it?
-I am going to provide you with the info that you asked for.
*PARADOX 4.5 on NOVELL
*Users accesing the tables using the forms.
*This has been going on for over 2 years but it has increased since last 2 weeks.
*No one has made any changes to network or application before these problem
*Users gain access through their NOVELL Network ID.
*Users can make chages to the data and it is saved when left the database.
*There is only one version of the Parados running 4.5.
What does deleting the Pdoxusrs.net file does? Also, i am not familiar with the TUtility that does data corruption check? Is these a program? and where can i find it?
-I am going to provide you with the info that you asked for.
*PARADOX 4.5 on NOVELL
*Users accesing the tables using the forms.
*This has been going on for over 2 years but it has increased since last 2 weeks.
*No one has made any changes to network or application before these problem
*Users gain access through their NOVELL Network ID.
*Users can make chages to the data and it is saved when left the database.
*There is only one version of the Parados running 4.5.
If you are using Pdox for DOS, Tutility is a separate program you will find in the same directory where you have installed Pdox. This program will fix corrupted tables.
If you are using Pdox for Windows, you will find it in one of the drop down menu, Table Repair.
Let's try this, kick or when all users are off Paradox, do a search for all *.lck and *net files. If there are any, delete them all.
I believe it's locking problem. Since this have been going on for 2 years, I am afraid you might have bigger problem. :-( Each time you exit Pdox abnormally, you run the risk of corrupting the tables.
Here is a test I used to use in Novell.
Create a test table on the network.
On one workstation (A), open the table.
Logon to another workstation (B).
Open the same table.
If successfull, put it in edit mode, add a record.
Put in some dummy values. Save it.
Go to workstation A, see if the record shows up.
If yes, try edit the record.
Basically, you are testing the locking of the table under a control environment. If you have encountered no problems. Then, your Pdox is set up correctly.
If not, then, you could have corrupted tables or your Pdox was never set up correctly.
You may want to consider getting some professional help.
Good Luck.
If you are using Pdox for Windows, you will find it in one of the drop down menu, Table Repair.
Let's try this, kick or when all users are off Paradox, do a search for all *.lck and *net files. If there are any, delete them all.
I believe it's locking problem. Since this have been going on for 2 years, I am afraid you might have bigger problem. :-( Each time you exit Pdox abnormally, you run the risk of corrupting the tables.
Here is a test I used to use in Novell.
Create a test table on the network.
On one workstation (A), open the table.
Logon to another workstation (B).
Open the same table.
If successfull, put it in edit mode, add a record.
Put in some dummy values. Save it.
Go to workstation A, see if the record shows up.
If yes, try edit the record.
Basically, you are testing the locking of the table under a control environment. If you have encountered no problems. Then, your Pdox is set up correctly.
If not, then, you could have corrupted tables or your Pdox was never set up correctly.
You may want to consider getting some professional help.
Good Luck.
- Thread starter
- #7
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question