Grazzhoppa
asked on
intermittent #error in a notes field in MS Access
I have a ms access front end (2003) and a sql server 2005 back end. I have about 100 users. There is notes field on the main form. 3 or 4 users have reported that about once a week they see #error in the notes. The field is varchar(1000) in sql server and memo data type in the access linked table. The control source is just the database field , there is no calculating going on. Users access the front end with a mde file. Most of them get access through a remote desktop. The remote desktop server has windows 2008 server(32bit) on it. Only one record at a time seems to have this problem and only the one field. The default view is "single form" so they only see 1 record at a time.
Apparently this has been happening for a while but went unreported. Closing the application and reopening fixes it. And I think just navigating away and back also fixes but havn't confirmed that yet. When I say fixes I mean the regular notes show up. I have been unable to recreate the problem ever. 1 person said they were running the mde from their local computer, the rest from the remote desktop. I make updates to the mdb and create new mde's about once a month. I always compact and repair before making the mde.
All my googling for #error only turned up problems with calculations and corrupt db's. And as I said there is no caluclating happening. Corruption seems less likely since I have a sql server backend. Any suggestions?
Apparently this has been happening for a while but went unreported. Closing the application and reopening fixes it. And I think just navigating away and back also fixes but havn't confirmed that yet. When I say fixes I mean the regular notes show up. I have been unable to recreate the problem ever. 1 person said they were running the mde from their local computer, the rest from the remote desktop. I make updates to the mdb and create new mde's about once a month. I always compact and repair before making the mde.
All my googling for #error only turned up problems with calculations and corrupt db's. And as I said there is no caluclating happening. Corruption seems less likely since I have a sql server backend. Any suggestions?
ASKER
I am using the sql server driver version 6.01.7601.17514
I would have used sql server native client 10.0 but none of the remote desktops actually had it installed. I can get it installed and update my dsn. Do you think this could help?
I would have used sql server native client 10.0 but none of the remote desktops actually had it installed. I can get it installed and update my dsn. Do you think this could help?
<Do you think this could help? >
Again, try the ODBC setting first.
This is a lot less disruptive than changing SQL drivers...
The published "limit" of concurrent users for a properly split Access database is 255.
In reality it may be closer to 50 or so.
So 100 seems to be pushing it a bit...
There are always folks who claim they are getting over 100 users, but t is never clear if all of these users can all log on and work at the same time (concurrent)
To be sure, does each user have their own copy of the Frontend on their local machine...?
Again, try the ODBC setting first.
This is a lot less disruptive than changing SQL drivers...
The published "limit" of concurrent users for a properly split Access database is 255.
In reality it may be closer to 50 or so.
So 100 seems to be pushing it a bit...
There are always folks who claim they are getting over 100 users, but t is never clear if all of these users can all log on and work at the same time (concurrent)
To be sure, does each user have their own copy of the Frontend on their local machine...?
ASKER
Yes each user has their own copy of the front end. No there is not 100 concurrent users. Probably not more than about 40 connections to the sql server database at one time but could be more. When you say "odbc setting" , are you referring to the timeout setting in Access? Im not sure what you mean. I don't see why changing drivers would be that difficult. I could just install it on a couple remote desktop servers. Then change the dsn that is used during table linking to point to the new driver.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
this problem was never resolved.
;-)
A lot of issue across Networks can do with Network delays or bottlenecks (timing issues).
Many times you can tweak the ODBC settings to minimize this.