That's true. Maybe I'll give it a test try on one of our customers and see how it works out. If I remove the prgs from the directory, I should remember. :)

One question, though. What do you do when SBT has a patch to one of the subprocedures? Cut and paste?

You've got a good idea, but it runs into problems with having two versions and only being able to associate with one. I was really looking for a command line option to VFP, but if there isn't one, it's no big deal.

As to the example project, I'd like to strangle the previous VAR. I'll give you a hint: they just changed their name to a tree. :) Count yourself lucky if you never end up with a customer from them!

Thanks,

Michelle


>Bad deal on inheriting the project like that! But seriously, when you've got a project that you've been a part of from the start, it's much less clutter and confusion to have the one big file.
>
>I guess though, if you really wanted to automate the process, you could create an EXE with VFP that issues a RUN/! command to call makeproc.bat, then compiles the resultant prg - that is if you're running VFP6 SP3. If you're bound to VFP5, then you could create an FXP that does the same thing. Then as long as your Windows file association is setup correctly, you could dblclick the file and it would launch fox and compile it for you.
>
>HTH
>
>-Matt