[AccessD] Eval function

the article says code like this:

Select Case (me.txtProcessingtype)
Case "Update"
	Call UpdateRoutine
Case "Delete"
	Call DeleteRoutine
Case "Add"
	Call AddRoutine
End Select

can be written
Eval me.txtProcessingtype & "Routine"

Jim Hale

-----Original Message-----
From: Michael R Mattys [mailto:mmattys at rochester.rr.com]
Sent: Tuesday, June 21, 2005 3:04 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Eval function


----- Original Message -----
From: "Hale, Jim" <Jim.Hale at fleetpride.com>
To: "'Accessd (E-mail)" <accessd at databaseadvisors.com>
Sent: Tuesday, June 21, 2005 3:04 PM
Subject: [AccessD] Eval function


> Okay, since it is quiet maybe we can start a discussion about the Eval()
> function. The article I just finished reading says  "The Eval function
lets
> you deliver applications that can create themselves dynamicaly at runtime.
> You can build your app code at runtime, pass it to the Eval statement, and
> have your dynamically generated line of code processed." Sounds
> interesting.Anybody use it?
> Jim Hale


Jim,

What else does this article say?
Why do I need the eval function if I've already
written the code to create a form, controls, CBF etc?

----

Michael R. Mattys
Mattys MapLib for Microsoft MapPoint
http://www.mattysconsulting.com

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

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.