D
David
I have a split db. BE is on SBS2000 server, clients are
mixed 98/XP all running Access 2k SP1. DB was recently
upgraded from 97 including the Tables on BE. After the
tables were upgraded we started seeing a problem. When 2
users update the same record they do get the usual write
conflict. If the second user selects to save record and
overwrite changes all the fields in the record seem to
change to ASCII characters and some fields change to
Chinese lettering (luckily this only affects the one
record not the entire table.). Thats right, I said
Chinese. Current program settings are: Table that stores
the record is quite large has approx. 252 fields and
12,000 records.The first field is autonumber no dupes and
set as index key. When this field corrupts it changes to
a negative number (something like -203984272). The other
fields appear to scramble and jumble (i.e. field 6 and 10
will combine and store in field 15). This poses a problem
because field 15 may be set as currency and text getting
converted to currency ends up as the net worth of Bill
himself! Once corrupted you can only delete the affected
record by compact/repair otherwise an error of 'key not
found' appears when you attempt to delete said record. I
know I am probably fishing here but, Anyone else have
this occur, or have any suggestions? Thanks.
mixed 98/XP all running Access 2k SP1. DB was recently
upgraded from 97 including the Tables on BE. After the
tables were upgraded we started seeing a problem. When 2
users update the same record they do get the usual write
conflict. If the second user selects to save record and
overwrite changes all the fields in the record seem to
change to ASCII characters and some fields change to
Chinese lettering (luckily this only affects the one
record not the entire table.). Thats right, I said
Chinese. Current program settings are: Table that stores
the record is quite large has approx. 252 fields and
12,000 records.The first field is autonumber no dupes and
set as index key. When this field corrupts it changes to
a negative number (something like -203984272). The other
fields appear to scramble and jumble (i.e. field 6 and 10
will combine and store in field 15). This poses a problem
because field 15 may be set as currency and text getting
converted to currency ends up as the net worth of Bill
himself! Once corrupted you can only delete the affected
record by compact/repair otherwise an error of 'key not
found' appears when you attempt to delete said record. I
know I am probably fishing here but, Anyone else have
this occur, or have any suggestions? Thanks.