Missing Records in Linked Table

[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

[Tom van Stiphout]

On Mon, 06 Aug 2007 20:17:20 GMT, "Neil" <no****@nospam. netwrote:

WAN? What exactly do you mean. Access is not designed to be used on a
WAN (using the standard definition thereof).

-Tom.

>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

[Larry Linson]

Tom,

Access client applications on the user's machines have worked for me, all
the way back to Access 2.0, via ODBC linked tables to server DBs on a WAN.
Performance can be a problem if there are very slow links (one company had
very slow response when multiple users at remote locations were connected by
256KB leased line, but response was acceptable to the users when they
upgraded to a T-1 connection).

I certainly don't recommend a split Access - Jet database across a WAN, but
some have reported even that was (at least minimally) acceptable for
occasional connections (The thought that came to my mind was "for very
patient users, perhaps." <GRIN>)

Larry Linson
Microsoft Access MVP
"Tom van Stiphout" <no************ *@cox.netwrote in message
news:4v******** *************** *********@4ax.c om...

On Mon, 06 Aug 2007 20:17:20 GMT, "Neil" <no****@nospam. netwrote:

WAN? What exactly do you mean. Access is not designed to be used on a
WAN (using the standard definition thereof).

-Tom.

>>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

[Neil]

And yet I use it, and it works fine. Imagine that!

"Tom van Stiphout" <no************ *@cox.netwrote in message
news:4v******** *************** *********@4ax.c om...

On Mon, 06 Aug 2007 20:17:20 GMT, "Neil" <no****@nospam. netwrote:

WAN? What exactly do you mean. Access is not designed to be used on a
WAN (using the standard definition thereof).

-Tom.

>>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

[Tom van Stiphout]

On Tue, 07 Aug 2007 04:48:32 GMT, "Larry Linson"
<bo*****@localh ost.notwrote:

For a moment I thought the OP was using an MDB over a WAN, but no, he
clearly states SQL Server 7. I wonder if the problem user has the
same version of the ODBC drivers and Office and Jet.
Could it be that the problem records are especially wide, perhaps with
varchars that are more fully populated, or memo fields?

-Tom.

>Tom,

Access client applications on the user's machines have worked for me, all
the way back to Access 2.0, via ODBC linked tables to server DBs on a WAN.
Performance can be a problem if there are very slow links (one company had
very slow response when multiple users at remote locations were connected by
256KB leased line, but response was acceptable to the users when they
upgraded to a T-1 connection).

I certainly don't recommend a split Access - Jet database across a WAN, but
some have reported even that was (at least minimally) acceptable for
occasional connections (The thought that came to my mind was "for very
patient users, perhaps." <GRIN>)

Larry Linson
Microsoft Access MVP
"Tom van Stiphout" <no************ *@cox.netwrote in message
news:4v******* *************** **********@4ax. com...

>On Mon, 06 Aug 2007 20:17:20 GMT, "Neil" <no****@nospam. netwrote:

WAN? What exactly do you mean. Access is not designed to be used on a
WAN (using the standard definition thereof).

-Tom.

>>>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

[Neil]

The machines are both using Access v. 9.0.0.6620, Jet 4.0.8618.0, and SQL
driver version 2000.85.1117.0. So I don't think it's a version issue (I'm
not checking their version of Office, itself, just Access).

Also, I looked at the data for one of the problem records, and all the
data's pretty short. There are two memo fields that contain 421 characters
and 252 characters. So that doesn't appear to be it.

Thanks,

Neil
"Tom van Stiphout" <no************ *@cox.netwrote in message
news:ot******** *************** *********@4ax.c om...

On Tue, 07 Aug 2007 04:48:32 GMT, "Larry Linson"
<bo*****@localh ost.notwrote:

For a moment I thought the OP was using an MDB over a WAN, but no, he
clearly states SQL Server 7. I wonder if the problem user has the
same version of the ODBC drivers and Office and Jet.
Could it be that the problem records are especially wide, perhaps with
varchars that are more fully populated, or memo fields?

-Tom.

>>Tom,

Access client applications on the user's machines have worked for me, all
the way back to Access 2.0, via ODBC linked tables to server DBs on a WAN.
Performance can be a problem if there are very slow links (one company had
very slow response when multiple users at remote locations were connected
by
256KB leased line, but response was acceptable to the users when they
upgraded to a T-1 connection).

I certainly don't recommend a split Access - Jet database across a WAN,
but
some have reported even that was (at least minimally) acceptable for
occasional connections (The thought that came to my mind was "for very
patient users, perhaps." <GRIN>)

Larry Linson
Microsoft Access MVP
"Tom van Stiphout" <no************ *@cox.netwrote in message
news:4v****** *************** ***********@4ax .com...

>>On Mon, 06 Aug 2007 20:17:20 GMT, "Neil" <no****@nospam. netwrote:

WAN? What exactly do you mean. Access is not designed to be used on a
WAN (using the standard definition thereof).

-Tom.
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
additiona l
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