[AccessD] May need an Unbound form

Stewart,

I am quite aware that testing with an unbound form will not help discover
why I am having locking issues.  Unfortunately I cannot reproduce the error
in my office, it is quite reproducible in the client's office 300 miles
away, I have been there, I have done everything I can figure out to do to
solve the locking issue (which should not even be happening as far as I can
tell) and just posted the circumstances to see if anyone HERE had seen this
or had any input on the locking issue.  I am NOT attempting to test the
locking issue by doing an unbound form.

Given the inability to solve a locking issue that shouldn't be happening I
am moving on to try to use an unbound form to take the new record data entry
and store the data.  I now have an unbound form accepting all the data so
the ONLY point of this entire thread is to see if anyone has ever seen this
locking issue using BOUND forms where many people are in a very small table
at once, entering new records all day long.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Thursday, March 31, 2005 8:34 AM
To: Access Developers discussion and problemsolving
Subject: RE: [AccessD] May need an Unbound form


On 31 Mar 2005 at 8:23, John W. Colby wrote:

> In fact what I am trying to find out is hwy the locking issue occurs 
> and how to get a bound form to cooperate.
> 

In that case, testing with an unbound form won't help.
The AllowEdits property of the form just sets all controls on it to 
ReadOnly. It does it's work long before any attempt is made to lock records 
etc.




-- 
Stuart


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