> > 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
>
> 1. Keep only 1 public variable - aka oApp application object
> 2. Hungarian notation is a preference, use or do not use. But do use m. (aka MDOT) prefix for memory variables.
> 3. ..
> 4. Obtain a book from Hentzenwerke.com to get the basics.
> 5. When asking specific questions provide reproducing code and preferably some data along with your post (check FAQ section for a code that creates a code that you can paste to your post for sending data from your tables).
>
> My .02 cents:)
>
> Cetin Basoz

Why use M.(MDOT) variables?

Leslie Botchway
Ghana