N
Neil
I'm running Access 2000 with a SQL 7 back end, using ODBC linked tables in
an MDB file. The db is used by about 30 users on a LAN, and an additional 10
or so on a WAN.
Recently, one of the WAN users complained of intermittently not being able
to find certain customers in the customers table (contains around 40,000
records). There are specific "problem records" of customers that can't be
found, and they all start with the letter "F" (the table has a numeric
customer ID as its primary key).
For these three or four customers that have been identified so far as
problem records, the customer exists in the customer list (a drop-down based
on a front-end table), but, when trying to go to the record, are told that
the record's not found.
Similarly, when the user searches for one of these problem records using the
custom search function, which searches the linked tables, the search
function says the record cannot be found.
Note that this is an intermittent problem with this single WAN user, and no
other users (on WAN or LAN are having this problem).
Any ideas about what might be causing it, or what can be done to this single
user's machine to alleviate the problem?
Thanks!
Neil
an MDB file. The db is used by about 30 users on a LAN, and an additional 10
or so on a WAN.
Recently, one of the WAN users complained of intermittently not being able
to find certain customers in the customers table (contains around 40,000
records). There are specific "problem records" of customers that can't be
found, and they all start with the letter "F" (the table has a numeric
customer ID as its primary key).
For these three or four customers that have been identified so far as
problem records, the customer exists in the customer list (a drop-down based
on a front-end table), but, when trying to go to the record, are told that
the record's not found.
Similarly, when the user searches for one of these problem records using the
custom search function, which searches the linked tables, the search
function says the record cannot be found.
Note that this is an intermittent problem with this single WAN user, and no
other users (on WAN or LAN are having this problem).
Any ideas about what might be causing it, or what can be done to this single
user's machine to alleviate the problem?
Thanks!
Neil