[AccessD] Development Cycle BE Question

There's no substitute for working with the client's own data.  For 
development or enhancement of existing apps. 

But if you need to make changes to the structure of the data then you 
have a coordination problem. 

I find the best way is to write a small app that makes those 
transformations to the back end database.  Then, as the client updates 
you with their latest data you can transform the old database to the new 
one.  And at the end, when you send them the new app, you can send them 
the transformation app as well so they can run it on their data.  It 
also has the side effect of consolidating all of your back end changes 
in one place. 

Hope that makes sense.  It's late.

Rocky


Joe Hecht wrote:
> As I develop the project I am working on, I am rudely
> reminded that the data I have been working with is from last
> September.
>
>  
>
> I may need to take the old tables with the current data and
> slice and dice them again to normalize.
>
>  
>
> How many of you while developing take clients data back end
> data so you are working with the most current data while
> doing pre lease builds?
>
>  
>
> Does this question make sense?
>
>  
>
> Joe Hecht
>
> jmhecht at earthlink.net
>
>  
>
>