>
>Oh, wow! I had this terrible happening in VFP where a similar change was required from 12,2 to 12,4 and all hell broke loose I had to lookup each and every table for similar fields and had to change them all table (weep) by table (weeping). That was the reason I have started using doubles in my tables (it's nto my HDD space and anyway it is cheap now), just set the picture in the preference box and the classes will adapt accordingly.

Actually, a double will take only 8 bytes, less than a numeric 12 or 15

>
>I guess, with domians VFP has nothing to worry about? for VFP it will still be a numeric type.

Yes, from what I've seen

>
>Thanks a lot, this I would not have learnt easily and in the short terms future.
>
>While I am writing this to you can I ask a direct question to you regarding FireBird (it is a sort of repeated, more like revisited)
>
>- I have a fbd created on my development machine. (for eg. contains mAccounts the master table)
>- I distribute this new fdb to the clients machine as an .SQL file created in Marathon which is then made into a fdb.
>- On the clients machine my support staff creates a table aAccounts (this is a flexible table logic I am implementing) which contains client specific fields regarding the master table
>- I update the application with / without updates to the fdb
>- I redistribute the app and fbd as an .SQL to the clients machine.
>- Support staff uses Database Comparer to compare the clients fbd with the new .SQL
>- The resulting update.sql contains the drop table command for aAccounts
>
>Though this can be manually overridden by removing the line from result.sql, I am not confortable with the chance that the support staff makes a mistake.
>
>Is there an opensouce/freeware no limitation utility to do the same maybe generate a result script without intervension from command line. The script then can be studied using a small command line utility to strip the drop table a... commands. Another utility then applies the changes from this updates script onto the clients fdb.
>
>Please advise.

Sorry, I don't know about something like this. I intend that, in my case, the application to handle changes in main database, by maintaing a special table (included in EXE) with tables versions and write migration code by hand or data driven. If you find something more simple, please let me know.