> > "This looks like a very good idea for new projects..."
> >
> > George,
> >
> > When you have the sizer that you want, why not retrofit your old forms. Create your new form class (inlcuding the sizer) and then open your form as a table and change the form's classlib and class name:
> >

> > USE [Path2\MyForm.SCX] IN 0 EXCL ALIAS MyForm
> > SELECT MyForm
> > LOCATE FOR BaseClass = [Form]
> > REPLACE Class WITH [MySizerFormClassName], ;
> >         ClassLoc WITH [FulPath2\MyBaseClassLib.VCX]
> > USE IN SELECT([MyForm])
> > 

> >
> > With VFP, just about everything is a table. Using ADIR() you could write a little program that looped through all of the forms in you Forms directory and change the class and classlib to your new new sizerform class.
> >
> >
> > Ken
> > You shall know the truth - and the truth shall set you free. (John 8:33)
>
> This is real good for application wide changes Ken!
> Question:
> Is it OK to insert "records" e.g. Command buttons
> If yes, What are the rules for assigning values for UniqueID and timestamp.
>
> George

George,

To tell you the truth, I have never even attempted inserting a record for a command button. I suppose you could as this is just another table. I normally only hack a form when this is the only way to do something. If I want to add a command button, I do it visually.

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)