SET PATH is way2dangerous, IMO !!

Nasty habit of opening the WRONG pricing file, or finding an archive copy, or whatever!

I much prefer to paramaterize the data path and default to it, because it gets completely blown away on the next set defa, while I can safely leave my system files on the search path. ( PLUS, a same name file in DEFAULT will be found first, which is usually what I want! ) Set path additive has a habit of finding the wrong one!

pathing ( with complex multiple companies and directories ) isn't a good choice when you have to keep directories 1 and 3 but refresh 2, so I tend to SET DEFA to the clients, and let the system path back to the common files.

nice thing about the parametered path is, it works very well with those mis-behaved COM objects that seem to fire up in a different directory every time you install them !