[AccessD] Dynamic SQL statement

[Stuart McLachlan]

We all get blindspots. I've just come across one.  

For years, we've been storing essentially identical data in two sets of columns depending on 
what Province the primary record belongs to.  (Don't ask - I didn't design that, it was 
someone else's add on)

That has required different data screens and  variations on 3/4 of the CRUD procedures on 
the primary records.

Just realised that I can combine these data points and simply everything considerably.  Just 
need to change the data labels on the front end depending on Province, but use the same 
procedures for all records.

Doh! again.



On 7 Dec 2015 at 23:23, ssharkins at gmail.com wrote:

> 
> Yes... you´re absolutely right. When I was actively writing and
> supporting db development, I often championed the superiority of
> recordsets. I´ve just forgotten... pity. 
> 
> 
> 
> 
> Susan H.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Doh!  That's the trouble with starting from a pre-conception.
> 
> A DAO solution is probably easier than SQL in this situation.
> 
> -- 
> Stuart
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com