Comparing Record Change Unbound Form

[Guest]

I am using an unbound form, so now AfterUpdate event is not applicable for the record/form. Is there a quick way to check if a field value has changed without having to trigger a proceedure for each field?>

I am assuming it is something like running each field against the recordset and seeing if the values are different?

 

[MacDermott]

Since your form is unbound, you'll have to make your own method of
associating it with a recordset.
One possibility which might help would be storing the fieldname for each
control in its tag property.
You'd still need some way to identify the correct record in the recordset...

DLookups can be useful in such a case, as can disconnected ADO recordsets -
but really, in most cases Access works best with bound forms.
Why build an elaborate structure to reproduce what Access already does
so well?

- Turtle

I am using an unbound form, so now AfterUpdate event is not applicable for

the record/form. Is there a quick way to check if a field value has changed
without having to trigger a proceedure for each field?>

I am assuming it is something like running each field against the

recordset and seeing if the values are different?

 

[Guest]

I am transitioning out of Access within the next year or so. My app is huge, and I am going to work through the process of unbinding everything, and switch to ADO as well eventually, so I can move the back end to SQL, and develo VB front ends, ASP etc...


Access is GREAT, but not for broad distribution, and we are selling loads of this product.

 

[MacDermott]

I'd like to suggest that you are making yourself a huge amount of work
without much value.
VB controls do not expose the same events as Access controls, so the
techniques which work in Access will not, in general, work in Visual Basic.

Here's my two cents' on how to manage your transition:
Leave your Access application as it is.
Write a VB front end, using ADO to access the same Jet tables you're
using now.
Then, if need be (I haven't heard an explanation of the need for this),
upsize the Jet tables to SQL Server. (There's a wizard which will do this
for you.)
If you need an ASP front end, write that.
If the application works well in Access, I'd suggest leaving the data
tables in Jet. MDAC (which comes installed on every OS from Win98 on) is
all you need to access a Jet table - quite a savings to your customers over
having to purchase a SQL Server license to run your product!

HTH
- Turtle

I am transitioning out of Access within the next year or so. My app is

huge, and I am going to work through the process of unbinding everything,
and switch to ADO as well eventually, so I can move the back end to SQL, and
develo VB front ends, ASP etc...