[AccessD] Unbound Form Check For Changes

Dan Waters df.waters at comcast.net
Mon Mar 24 09:24:56 CDT 2014


Hi John,

I sincerely want to suggest that you write a how-to book on class usage in
Access.  Your blog postings are a great start.  I don't believe I've ever
seen anything commercially available like that.

You can write it and sell it as an e-book on Amazon - you will get sales.
You have a unique skillset here that you have developed with a lot of effort
- it's time to get some reward!

However, having watched my father write his 5th book, he still needed a good
editor, and all authors do.  So write out the introductory chapter, post it
here and we'll all give feedback - for free!  

All the best!
Dan

PS - I think you'd actually be doing many thousands of businesses a big plus
- they will be able to get much better use out of a tool they already own.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W Colby
Sent: Sunday, March 23, 2014 8:02 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Unbound Form Check For Changes

And having done all that stuff, I would go with a class.  All of the code to
check old value = new value, a dirty flag and so forth can be stored in the
class.

John W. Colby

Reality is what refuses to go away
when you do not believe in it

On 3/23/2014 7:04 PM, Bill Benson wrote:
> Re: Dirty, even if bound, a change would mean the user began to edit 
> the form, not that they necessarily "made" a change.
>
> As for storing the control values, if all you care about is testing if 
> ANY controls changed, I would put a tag in every control where this is 
> a possibility and loop through all controls, test for this tag - then 
> you won't have to worry about labels and controls with no value 
> throwing off a runtime error. I would just store all values in a 
> single string using a pipe separator, and check this again later.
>
> 'Warning air code!!!
> Option explicit
> Dim m_Initial_Control_Values as String
>
> Form_Load()
> For each ctrl in controls
>     If ctrl.tag = "ValidateMe" then
> 	m_Initial_Control_Values  = _
> 	m_Initial_Control_Values  &"|" & NZ(ctrl.value,"") &"|"
>      End If
> Next
> '...
> End Sub
>
> Have a function named FormChanged
>
> Function FormChanged() as Boolean
> Dim strValidate as string
> For each ctrl in controls
>     If ctrl.tag = "ValidateMe" then
> 	strValidate  = _
> 	strValidate &"|" & NZ(ctrl.value,"") &"|"
>      End If
> Next
>
> FormChanged = (strValidate <> m_Initial_Control_Values) End function
>


---
This email is free from viruses and malware because avast! Antivirus
protection is active.
http://www.avast.com

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



More information about the AccessD mailing list