[AccessD] Unbound forms

Hi Michael:

In most cases, it is not necessary to use unbound records with MDBs. Unbound
forms work much better with larger sequel DBs that have their own internal
data management systems. (transaction logging and roll-back.)

If you are using unbound forms you will have to manage the locking through
the recordset(s) that actually access the data. The basic methodology is:

1. The specific record called should use the dynamic-link method.
2. Set the 'lock-record' property.
3. Monitoring the resultant error codes when accessing and especially when
attempting to delete or updating. Take the appropriate action...(inform
user, pause and retry, abandon, overwrite, write code to handle differences
between the fields of the updated and current record(s) etc.)

Time-stamping a record can be important in managing data conflicts,
backup/archiving copies on mission-critical systems is another process
worthy of consideration and transaction logging. (These can be good reasons
for rolling-your-on unbound application.)

If you decide to go this route and have a specific question, I can help you
out.

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Michael
Brösdorf
Sent: Friday, July 02, 2004 7:30 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Unbound forms


Dear group,

there was a lot of messages concerning bound forms vs. unbound forms every
once in a while on the list - I don't want to get the discussion about pros
and cons started again ;-))

My question is: is there any comprehensive resource on the web showing a
proven design of unbound forms?
(e.g. how to update records, how to identify/handle conflicts in multi user
environments, error handling etc.)

Michael

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