>No I didn't miss it. I'd forgotten that you used it. I'm just admitting that I don't know SBT, but I would be astounded if they required the developer to distribute their files in individual tokenized programs. Further, in the case of forms, having the SCX/SCT files out there subjects them to possible corruption that couldn't occur if they were part of the executable.

I'm not sure why the fact that I use it is relevant, but ok. :) At any rate, I don't know if it's a requirement, but the fact that when you install Pro Series from the CD it installs as individual files makes it hard to not distribute that way. We would have to intercept the CDs, install them locally, compile it all into an EXE, then put that EXE on to another CD to send to the client. Seems like a lot of extra work for not much benefit. LOL!

>Well, back in the FoxBASE days, someone modified the PRG, either intentionally or not, those changes were part of the program. I don't know whether or not the following is a concern or not, but what would a VFP 6.0 SP3 or later do if there was a DO command that referenced a prg file that had a later date/time stamp on it than the corresponding fxp? Would it re-compile automatically?

I know it will recompile if the FXP is missing. Not sure if the timestamp is different. I always upload both the PRG and the FXP when I do an update.

>Besides, even if it doesn't it means that you've further slowed the process down. I don't know if this is still the case on all Windows platforms, but, AFAIK, file names aren't stored in order, and the OS has to do a squential search to locate the file. The more files, the longer it takes for Windows to locate the correct one.

I can't speak to perfomance issues as I've never tried to compile it, but given the reply I got from John on this thread, it seems like it doesn't make a big difference.

Thanks,

Michelle