[AccessD] VBA Unbound data entry / update form

ROTFL.  I am a programmer, I know DAO and can write it 
freehand in my sleep.  I don't choose unbound under normal 
circumstances simply because bound exists, and is done at 
the JET level, tightly integrated with forms and controls.

In all of my years of doing Access, I have exactly TWO 
places (a single form at two different clients) where I hit 
this JET / MDB wall.

One is in a call center where the users are calling out all 
night.  A dozen or more people, all in the same form, 
entering new records in the same table, records about calls 
they are making.

The other is in a call center database, where users pull up 
a form to enter information about calls they are making (and 
  occasionally other kinds of communications such as faxes, 
emails and letters).

In both cases, lots of people are entering records 
simultaneously into the same table.  In both cases, the 
forms have a few memo fields where the data is entered (the 
probable culprit) and in both cases there are several 
indexes on other fields in the table.

In both cases I have done the normal troubleshooting of JET 
locking methodology, record level locking etc.  In BOTH 
cases, NEW records cause "record locked" error messages to 
the user trying to enter the new records.  This indicates to 
me that it is a "page locking issue" rather than a record 
locking issue, and the reported errors are the good old JET 
bad message syndrome.

In this thread I was really just taking the opportunity to 
let the secret order of the UHU show their stuff.

It certainly appears that I will roll my own.

John W. Colby
www.ColbyConsulting.com


Edward S Zuris wrote:
>  It can be done.
> 
>  You'll have to use a lot of VBA, take care of the
>  record selection.  Become acquainted with .Addnew,
>  .Edit and .Update.
> 
>  And you have to put some of the Microsoft way of
>  thinking to one side and think of the programmer
>  way of doing things.
> 
>  Many with criticize that way of doing things.
> 
>  However, if you have someone paying you to do such,
>  and the check clears the Bank, who cares.
> 
>  It will take longer because of the extra coding.
> 
> 
>     ' *****************************************************
>     ' Store the SQL Select for exported records.
>     '
>     rsSetB.Edit
>     rsSetB![ExportSQL] = sPhyTableSQL
>     rsSetB![Output] = sExportFile
>     rsSetB.Update