I'm putting together a GUI to automate the whole module plug-in & plug-out. I just posted to the BCX group a help question. When I get the answer I will finish putting it together and upload it with a bunch of other neat things. HA! This is all moving forward many times faster than I ever thought it would! John --- John Jacques <johnj_01201@xxxxxxxxx> wrote: > > P.S. I redesigned the fox2csv.bas program to use this new format > already. I'll upload it in a few minutes in case you want to check > out > the design of it all. > > Hello, back in the old days when I only programmed in Assembly > Language > I had my computer set up perfectly. I had one program that had over > 30,000 lines of code and I never lost track of how it worked or where > to fix a bug when something went wrong. No, I wasn't that smart, I > just > had a really neat development enviroment set up. > > Every programmer has their own way of doing things. > > This is what I am doing now, especially since I have so many > interchangeable SUBS to use in different programs. > > 1) Each sub is in it's own file. > 2) The sub has a name sample() which is the filename. > 3) The sub is categorized and placed in the SUBS directory tree where > it belongs. The tree is prefixed to the filename for that sub, and > also > to the subs name. (see demo below) > 4) A batch file (build.bat) is used to copy all of the subs into one > filename.bas which is then compiled as normal in BCX. > > The batch file goes like this: (watch Line wraps) > --------------------------------------------------- > del Build\*.* > copy "..\SUBS\FileIO\FileIO_Sub_Name1.bas" + > "..\SUBS\FileIO\FileIO_Sub_Name2.bas" + > "..\SUBS\FileIO\FileIO_Sub_Name3.bas" "Build\projectname.pt1" > etc.... > copy "..\SUBS\FileIO\FileIO_Sub_Name1.bas" + > "..\SUBS\FileIO\FileIO_Sub_Name2.bas" + > "..\SUBS\FileIO\FileIO_Sub_Name3.bas" "Build\projectname.pt8" > etc. > > copy "Build\projectname.pt1"+ "Build\projectname.pt2" + > "Build\projectname.pt3...8" "projectname.bas" > > ------------------------------------------------ > > This keeps all the subs in nice and organized, the Build.bat file > copies all the sections of the program into one filename.bas for > compiling. > > It will also, automate a flowchart with some details on each module > such as the purpose and calling\returning requirements. > > I've just started setting it all up. > > I don't know if you can see the "big picture" here, but it is all > leading up to reuseable modules that can be plugged into place with > ease. > > I am going to attempt a GUI to take care of the .batch file and all > the > modules. So clicking would plug or unplug a module and you would not > have alot of work to do manualy. > > John > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com