One thing no one else mentioned. In FPD and FPW it was traditional to do a SCATTER MEMVAR or SCATTER MEMVAR BLANK on the way into a screen, then edit the memvars, and then GATHER MEMVAR or INSERT INTO... FROM MEMVAR. This was to eliminate record locking problems among other things.

Now in VFP you can use SCATTER NAME to get an array of the names of your table fields which might be attached to a data object, and then scatter the values that go with the names. The other thing to do in VFP is work with the fields directly in the view, and do a buffered update from the view to the actual table.


>I keep running across examples of code that occasionally prefix variables with m. (ie. m.nTablesUsed = AUSED(aTablesUsed))
>
>I've been trying to figure out what the signifigance of the m. is in the context of the code, but it's hasn't clicked yet. All of the books I've been reading provide examples of code using it, but none have explained the purpose. (My guess is that's it's so elementary they didn't think it needed to be explained, which may be true, but there are always a few in the crowd that happen to be more dense than the rest =)
>Can somebody please enlighten me? (Or, if it's a lengthy explanation, point me to documentation...)
>
>Thanks!