[AccessD] Possible Causes for #ERROR# in datasheets fields.

Thanks Marty,
 The error is not user, machine or even company specific. Subdatasheets
are turned off. So maybe a locking problem...
 Hmmmmmm

Thanks !!
Robert  

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Thursday, April 28, 2005 9:16 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Possible Causes for #ERROR# in datasheets fields.

Couple of guesses have you turned off subdatasheets on backend table,
the default is set to on when creating.
Could be OPs series Lock problem if Win 2000 and if both client and
server not SP3.
http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html
There is more about it here
http://www.granite.ab.ca/access/tipsindex.htm

Could be a flakey NIC.
I assume A2K is SP3. and Jet SP7 or 8
Compact the back and front end and break then rebuild the links, the
backend cache can get a lot of garbage in it.

Robert Gracie wrote:

>Hello,
> Occasionally, the user will be entering data, and when moving 
>(Tabbing) to another field they are getting this #ERROR# across all the

>fields in a datasheet. Sometimes they are getting this error along with

>an msg about someone else has change the current record, but there 
>would be no other users in the system.
>
> The only way to get the error to go away is to close the form and
re-open.
>After which, there is no evidence of any problem.
>
> It was noted, that is seems to happen more, when the user is entering 
>the first record to the datasheet dataset.
>
>A2K Split FE/BE
>
>Any Clues?
>
>  
>

--
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com