>OK, *NOW* I get it, thanks a lot.
>

Great! I've got some ideas you might want to play around with, depending on how you application is set up to behave.

You needed add an additional executable file; you could build this functionality right into the body of your application, where it gets triggered by a command line parameter passed to the main program, which starts up some registration and initialization code. Some ideas for useful switches:

REGLOC - reads the current executable path and sticks it in the registry
ADDUSER - grab the current UserName and create user-specific things to the registry, as well as shortcuts on the current user's DeskTop and Start Menu (nice under NT and Win9x with user profiles, where each user has his own!)
INITDBF - fires up a dialog that goes out and creates the empty tables/DBCs, etc needed to make yourself a new data directory, and save that information in the registry.
BUILDCONFIG - creates a user- (or at least station-) specific CONFIG.FPW, making a best guess at the best place to put the tempfiles, etc.

You can obviously add to the list, but the idea is that there are parts of the app that aren't appropriate to integrate into the GUI (or may be, but they also need to be availble in a non-interactive mode, too) that can and probably should be available somewhere. When the interactive version of these things needs to be a part of the application, it makes sense to expose them with the batch interface as well - the modifications are easy, and the code can be maintained in one (admittedly monolithic) project.