[AccessD] "Record is deleted" error

We've had discussions about bound and unbound?  Funny, I don't
recall.... ;)

What that debate finally boiled down too was that bound controls provide
a lot of functionality built in, that if you only need that
functionality, why re-invent the wheel?!?!

In my case, I rarely built a form or interface that didn't need some
sort of special tweaking.  In fact, I rarely built entire systems.  When
I did build a complete system, I usually had classes and collections
setup to handle all the business logic with code, so it was necessary to
use unbound forms and controls to interact with the data intensive
classes. Bound forms would go around my business logic.

I guess a bound control is like walking into a dealership and buying a
Lexus with a warranty.  It'll get you where you want to go in style.
Unbound is like building a muscle car in a garage.  When you are done,
you know every nut and bolt and what it does.  When you drive it, you
can picture every single element that you put in place, working
together.  Problem is that there are dealerships that sell lemons, and
home built cars that fall apart after ten feet.  So some experiences
have jaded people.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl
Collins
Sent: Wednesday, May 26, 2010 6:56 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] "Record is deleted" error


________________________________________________________________________
_______________

Note: This e-mail is subject to the disclaimer contained at the bottom
of this message.
________________________________________________________________________
_______________


Definitely agree on splitting out Memo fields.  Also try pulling data
into the form using a "Just in Time" approach.  Be careful when using
bound tab forms as the user may only use one of the tabs (out of
dozens), but all the data is still being pulled into those other unused,
unseen or hidden tabs.

"Unbound seems like it will be the ultimate answer".

Yep, the deeper I get into this Access Database business the more and
more I find I make the forms unbound and only when the user is ready to
save the record (by pressing a save button) do I write the data back
into the source table using a recordset.

It takes a bit more work in the code to setup, but the gains in
stability, speed and reliability are well worth it IMHO.

I know there have been some, ummm, interesting discussions on here about
bound vs unbound but I am finding unbound is the way to go.

Cheers
Darryl.
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.