Hi all,
I've been having intermittent problems with the composite rules file at a client's office. Today it was particularly bad.
The problem started to show up after a new table was added to a set, and even though this table is just READ, not written to, when accessed through this set, something is amiss.
Short-term solution is to just delete the .rlc file for the set, but the problem will happen again after a while. Longer term solution has been to take the new table (images.dbf), copy all records to a temporary table, zap the original, and then append the records back from the temporary table.
Could anyone please shed some light on HOW the rlc file is created, WHEN it is updated (if at all) and under what circumstances, and WHAT would corrupt it?
I will consider anything you can come up with, up to sticking a slice of onion in the cd drive of the server.
This problem has proven to be VERY elusive, because alpha doesn't return an error message when the rlc file is corrupted, but as soon as someone tries to open the set SINCE the rlc got corrupted. For example, users A, B, and C start working at 8am and stay in the set. The rlc gets corrupted at 9:30am. User D tries to open the set at 11:10 and gets the error, but A, B, and C are fine. After this, no one besides A, B, and C can work in that set.
Another theory is that D is the one that corrupts the composite rules file, but the problem still remains: WHY is the file being corrupted????
Thanks for your help!
Alex
PS: Windows 98 stations. Novell SBS 4.11 server.
I've been having intermittent problems with the composite rules file at a client's office. Today it was particularly bad.
The problem started to show up after a new table was added to a set, and even though this table is just READ, not written to, when accessed through this set, something is amiss.
Short-term solution is to just delete the .rlc file for the set, but the problem will happen again after a while. Longer term solution has been to take the new table (images.dbf), copy all records to a temporary table, zap the original, and then append the records back from the temporary table.
Could anyone please shed some light on HOW the rlc file is created, WHEN it is updated (if at all) and under what circumstances, and WHAT would corrupt it?
I will consider anything you can come up with, up to sticking a slice of onion in the cd drive of the server.
This problem has proven to be VERY elusive, because alpha doesn't return an error message when the rlc file is corrupted, but as soon as someone tries to open the set SINCE the rlc got corrupted. For example, users A, B, and C start working at 8am and stay in the set. The rlc gets corrupted at 9:30am. User D tries to open the set at 11:10 and gets the error, but A, B, and C are fine. After this, no one besides A, B, and C can work in that set.
Another theory is that D is the one that corrupts the composite rules file, but the problem still remains: WHY is the file being corrupted????
Thanks for your help!
Alex
PS: Windows 98 stations. Novell SBS 4.11 server.