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 5 2779
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,
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
And yet I use it, and it works fine. Imagine that!
"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
On Tue, 07 Aug 2007 04:48:32 GMT, "Larry Linson"
<bo*****@localhost.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
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.com...
On Tue, 07 Aug 2007 04:48:32 GMT, "Larry Linson"
<bo*****@localhost.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
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Oren |
last post by:
Hi,
I have an Access application with linked tables via ODBC to MSSQL
server 2000.
Having a weird problem, probably something i've done while not being
aware of (kinda newbie).
the last 20...
|
by: David |
last post by:
Hi,
I have an order form which has a field 'ProductID'.
This form has a button on each record to open a new form linked by
ProductID.
This new form is a continuous form and obviously, only...
|
by: Rashapoo |
last post by:
I have just completed a basic course in Access. I have some relational
b/g in DB2 and Cobol. I have a question my instructor couldn't answer
(or maybe I didn't explain myself)
I design a...
|
by: csgraham74 |
last post by:
Hello,
im using MS Access as a front end to link to MYSQL. although this is
possibly an Access issue i thought someone would be able to help me.
the error message "ODBC--insert on a linked table...
|
by: sparks |
last post by:
I am trying to fix a database that someone did about 4 yrs ago in
access97.
The main table just contains demographics and is on the main form of
the database.
It has a subform on a tab that...
| |
by: gerbski |
last post by:
Hi all,
I am relatively new to ADO, but up to now I got things working the way
I wanted. But now I've run into somethng really annoying.
I am working in MS Access. I am using an Access...
|
by: wvmbark |
last post by:
First time poster... I just found this forum and it appears there's plenty of people here that could make short work of problem that's been driving me absolutely bonkers for months.
Every day we...
|
by: Charlotte |
last post by:
Hi,
i've googeled to find a asp-script that can compare all the records in two
different access databases
the mdb's have exactly the same tables
what i want is that (the output) all the...
|
by: scott.tang |
last post by:
I'm experiencing a very strange problem. My application is MS Access
front-end and MS SQL server back-end database. I have a SQL statement
that deletes records from a table after an export...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
| |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
| |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence...
| |