What? You mean - copy the whole system down to my C: drive - instead of
developing on the Network???
Which - if I do - will cause More headaches - if the Other Bozo here
actually has to work on this system at the same time I am...
1. If the other bozo is actually working on it the same time you are, you
can't compile it. VFP has to have exclusive access to the files to compile
them.
2. If the other bozo and you are going to work on aspects of the same
project at the same time, then you need a source control system, or you're
going to end up with some very ugly surprises.
3. But no, just copy it down when you want to compile, and then copy the
compiled file(s) back up. As others have said, you can do a lot of testing
by running stuff in the IDE before an actual need to compile arises.
4. And see my response to Alan; the problem may be hardware-related and the
only way you can find out is to compile it locally for a while and see if
the problem recurs.
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/5.2.1.1.1.20130415122652.01c77...@pop-server.stny.rr.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
