[AccessD] Filtered combos

jwcolby jwcolby at colbyconsulting.com
Thu Mar 5 10:30:40 CST 2009


SQL is one of those places where caching the strings wouldn't help simply because the execution of 
the SQL would dwarf the load time of the sql string.  Caching only does good where the time to get 
at the uncached data would significantly slow down the process using the data.

John W. Colby
www.ColbyConsulting.com


Charlotte Foust wrote:
> We actually do something related in our .Net products.  We store special
> purpose SQL in xml files with nodes for Read, Create, Delete and Update
> if necessary.  When we need to use it,  We read it out of the xml file
> add any necessary where clause and put it to use.  The details of
> reading the xml files are handled in classes but the class doesn't cache
> the sql because it doesn't really cost anything to read it out of xml.
> No database connection required or anything.
> 
> I have in past Access apps used a table to store SQL strings and used a
> class to retrieve the appropriate SQL and put it to use, but the details
> are buried in the dim past.
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, March 05, 2009 7:52 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Filtered combos
> 
> Mike,
> 
> I can see how this might be advantageous in some processes.  I have
> never actually done this before but I have read about the process.  I
> thought it was more for translating strings and such, or the ability to
> use a common string for message boxes, labels and so forth.  I never
> really thought of it in terms of holding SQL Strings.
> 
> Does anyone out there use this technique?  A class to cache these
> strings might be useful if you were going to use such a table.
> 
> If anyone uses it, what kinds of strings do you put in the table?
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Mike Mattys wrote:
>> OK, what I was thinking was that you'd have a global class that is 
>> instantiated while the database is open and you'd just call a method 
>> in the class with the record number of the string that would be the 
>> new recordsource of the combo.
>>
>> -
>> Michael R Mattys
>> MapPoint and Database Dev
>> www.mattysconsulting.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