Missing Records in Linked Table

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!
NeilAre they accessing the table directly or through a View that might be
limiting records?
--
KARL DEWEY
Build a little - Test a little
"Neil" wrote:

> 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 bas
ed
> 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 t
he
> 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 n
o
> 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 sing
le
> user's machine to alleviate the problem?
> Thanks!
> Neil
>
>|||No, directly, the entire table. Also, note that the functionality is fine,
and on one (and now I found out two) computers the data for those records is
intermittently not there. But on other computers it's there. Nothing in the
functionality that would be limiting it.
"KARL DEWEY" <KARLDEWEY@.discussions.microsoft.com> wrote in message
news:3D9F901F-12EB-479D-9981-AE808A4E76EB@.microsoft.com...[vbcol=seagreen]
> Are they accessing the table directly or through a View that might be
> limiting records?
> --
> KARL DEWEY
> Build a little - Test a little
>
> "Neil" wrote:
>|||hi Neil,
Neil wrote:
> Note that this is an intermittent problem with this single WAN user, and n
o
> other users (on WAN or LAN are having this problem).
Check thw WAN connection and the service packs (OS, Office, MDAC/Jet) of
the client.
mfG
--> stefan <--|||Hi, Stefan. I am tracking the version of Windows, Access (msaccess.exe), Jet
(msjet40.dll), and the SQL driver (sqlsrv32.dll), and they are all the same
as the other users. Are there any other files you suggest I check?
The fact that these records all have names starting with "F" leads me to
wonder if it's a paging issue, even though the PK is the customer ID, not
name, though there is an index on last name.
Thanks,
Neil
"Stefan Hoffmann" <stefan.hoffmann@.explido.de> wrote in message
news:uEy7$tM2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> hi Neil,
> Neil wrote:
> Check thw WAN connection and the service packs (OS, Office, MDAC/Jet) of
> the client.
>
> mfG
> --> stefan <--|||hi Neil,
Neil wrote:
> Hi, Stefan. I am tracking the version of Windows, Access (msaccess.exe), J
et
> (msjet40.dll), and the SQL driver (sqlsrv32.dll), and they are all the sam
e
> as the other users. Are there any other files you suggest I check?
No.

> The fact that these records all have names starting with "F" leads me to
> wonder if it's a paging issue, even though the PK is the customer ID, not
> name, though there is an index on last name.
Can you browse the linked table on that specific client?
mfG
--> stefan <--|||
>
> Can you browse the linked table on that specific client?
>
> mfG
Good question. I'll have to check on that tomorrow.
BTW, what's mfG?

> --> stefan <--|||hi Neil,
Neil wrote:
> BTW, what's mfG?
"mit freundlichen Gren" means "with kind regards"
mfG
--> stefan <--