Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 329
  • Last Modified:

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?
0
Grazzhoppa
Asked:
Grazzhoppa
  • 3
  • 3
1 Solution
 
Jeffrey CoachmanMIS LiasonCommented:
"Corruption" is a vague term that can apply to almost any gremlin...
;-)

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.
0
 
GrazzhoppaAuthor Commented:
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?
0
 
Jeffrey CoachmanMIS LiasonCommented:
<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...?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
GrazzhoppaAuthor Commented:
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.
0
 
Jeffrey CoachmanMIS LiasonCommented:
<"odbc setting" >
Not sure I remember where they were in Access 2003 (I think under "Advanced Options"

But there are a couple of setting there that might help...

You can change drivers if you like...

You can also:
Make sure the back end is compacted on a regular basis
Make sure that you compact the Front end on each revision (and compile the code)
You can even try creating a blank new db and importing all the objects
You can try Decompiling the FE and BE...
Make sure you have all service packs in stalled on the Server and all the desktops...

Again, without much to go on here, I can only throw out guesses.
0
 
GrazzhoppaAuthor Commented:
this problem was never resolved.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now