[AccessD] RE: Using classes - was Instant If Then Else

Paul,

In fact the whole thing took two days (so far).  One to analyze the field
map table and figure out how I was going to attack this, and one to write
the two classes and get them playing together.  The nice part is that there
is another completely different export that has to occur - different field
map table, different data from our end.  However all I have to do is build
my query that pulls the data, place the field names from my query into the
column in that field map table for my field names, in the matching records,
then call exactly the same program.  Tell it how long the string should be
this time and the name of the new field map table and data query, and the
name / location to place the file.  The exact same code works exactly the
same for the next export.  

John W. Colby
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Rodgers
Sent: Friday, August 13, 2004 4:08 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] RE: Using classes - was Instant If Then Else


Thanks, John. I'm dizzy from reading it through just once. That sounds an
enormous assignment - but what a sense of success when you reach(ed) the
other end. I hope the client was graeful. 

Cheers and thanks for both ideas. 
paul 

-----Original Message-----
From: Colby, John [mailto:JColby at dispec.com]
Sent: 12 August 2004 20:24
To: 'Access Developers discussion and problem solving'
Subject: Using classes - was RE: [AccessD] Instant If Then Else


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