[AccessD] Development Cycle BE Question

On 16 Jan 2006 at 22:01, Rocky Smolin - Beach Access S wrote:

> 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. 

No need to write your own app, that's what the BackEnd Upgrader is 
for.

"The Backend Upgrader (BEU) is a utility that will allow developers 
to map out changes to their mdb Back End (BE) databases and deploy 
them remotely and automatically. .... This utility will allow the 
developer to avoid making changes to the BE by hand, on-site, or by 
remote link, and then possibly forgetting some vital change."

I have used the BEU to totally rebuild a BE that was denormalized, 
poorly named and bad data. It took 70 different versions of the BE 
and 200+ changes IIRC all done through the BEU.

You can get the BEU from 
http://www.databaseadvisors.com/downloads.htm

-- 
Bryan Carbonnell - carbonnb at sympatico.ca
Never put both feet in your mouth at the same time, because you won't 
have a leg to stand on.