> > Today I use VFP to improve my own productivity and distribute my work to a very small community.
> >
> > Foxite is a great resource for keeping me out of trouble, but someday I know I'll need to hire an expert to make my applications more robust and networkable.
> >
> > So I direct my query to you VFP consultants in Foxite land: What are the common coding practices that newbies make that I should avoid to make your consulting life easier?
> >
> > Three things I've heard on Foxite so far
> >
> > 1. Keep public variables to a minimum
> > 2. Use Hungarian notation
> > 3. Create your own subclasses of the VFP base classes
> > 4. . .
> > 5. . .
> >
> > Are there certain coding practices that make you want to tear your hair out?
> >
> > Dan Baker
> > Effort of the Poconos, PA, USA
>
> In addition to the Hungarian notation, i would suggest making field names unique across all tables within an application so that any queries created using "*" for the fields definitions yields field names matching the original table names (field1, field2, etc.) and not VFP generated names (field1_a, field 1_b, field2_a, field2_b, etc.). This is especially useful for creating on-the-fly queries.
>
> Garth Groft

I do that too.


Mike Yearwood