What are the Pros and Cons of Multiple EXEs

[jrumbaug]

I need some basic concept explained.

I have been asked to modify an aplication. It has been compied into multple EXEs with one module calling the next. I am having trouble getting it to run from the command prompt. I believe I need to recompile before my changes are seen, or the path statement is finding the compiled EXE before it finds my updated PRG. or something else. The question is, what is the advantage of multiple EXE programs and what is the disadvantage?

Jim Rumbaugh

 

[Mike Lewis]

Jim,

Personally, I've never seen a reason to use multiple EXEs, although I know other developers who do. I guess it provides a possible way to break a huge app into smaller modules. To me, it's always seemed more trouble than it's worth. I'd be interested to see what other folk think.

Mike




__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[wgcs]

You are correct: VFP "is finding the compiled EXE before it finds my updated PRG".

Whatever is inside the EXE will take precedence over any external .PRG/.FXP files.... even if you "DO MYPROG.PRG" or "DO MYPROG.FXP", VFP will launch "MYPROG.EXE" (or MYPROG.APP), if it is in the current path.


So, rename your EXE (or delete it if you have other backup copies) and then do your testing with your modified .PRGs

- Bill

Get the best answers to your questions -- See FAQ481-4875.

 

[jrumbaug]

Thanks Mike and Bill.

This app has code from the early 90's that has migrated to VFP8. I thought the multiple EXEs were from the early days of DOS and 640K memory limits, when you couldn't get something to load into memory unless you broke it into smaller chunks. But is there any advantage now, as in performance or in maintenance that makes this a prefered style?

Jim Rumbaugh

 

[Dan Freeman]

We use multiple exes, for multiple reasons. ;-)

When distributing fixes, our clients have less to download if a fix occurs only in one EXE.

More importantly, licensing. Many of our exes map to discreet functionality. Rather than coding elaborate "access" schemes, if they haven't licensed module "B" then they don't get that module and it never shows up on their menus.

It boils down to packaging and convenience.