Hi again, Cetin.

>Read my reply, This piece is not needed.

I read it, Cetin, and thanks for the info. As a matter of
fact, I was reading something very similar to what you wrote
in -- believe it or not! -- VFP help on SYS(2015) :^) :^).
Seriously, I read it yesterday, and when I read comments here
from varoius people, I'd like to think they have read up on the
subject (using VFP's help facility) and that they are stearing
me away from a path they've already been down and back again.
All I can say is that I RTFM :^), and as a newb to VFP, I will
sometimes need clarification from you, my mentors :^).

BTW, is it me, or do you people think the folks at Microsoft
go to some kind of "obfiscation and detraction writing school"
before Gates and company will let them write a help file or
manual? :^) :^). If any of you people have read the books
from Microsoft Press, you know what I mean :^) :^).

>OTOH sys(2015) duplication is not very slim (or even slim)
>in a multiuser environment.

As I have mentioned in other threads here on UT, we have a
situation where the app is either muli-user or a single
client. It all depends on whether the app has an Internet
connection or not. Also, should a collision take place,
we plan on adding VFP and MySQL code to e-mail us about
it via triggers and stored procedures. Will even add some
code to e-mail our cell phones, just for good measure.
(Man. That last sentence reminds me of the days when I was
both IT geek and programming geek at the same time, and my
Motorola text pager would go off at 3:22 AM or something.
NAK! :^)


>Even only 2 fast typist were able to produce it (given
>that you might have in code insert/imports
>computers surely increase that level to almost over 50%).
>Read this sys(2015) alone is never safe. Use GUID.

In all of our new apps, we're going GUID all the way, Cetin.
Thanks for the info, dude. Much appreciated. BTW, we really,
really appreciate everyones' input here, folks. Thanks a
bunch! :^)


Best Regards,

Randall