>>>My client wishes to distribute the app on CD. They will probably ask me what the options are. If they just want to install from the CD as if it was a stack of diskettes, I will have to get the stuff from the setup wizard onto the CD. If they want to actually run the app from the CD, I would have to make it install the .DLLs and runtime module, tell it where to put FOXUSER.DBF and .FPT, and tell my .app where they were put. Could someone please give me an idea of what is involved?
>>
>>
>>Does your application NEED to modify the foxuser table? If not, you can just leave it on the CD and hard code the location. Otherwise, create a config.fpw in the system folder and use that to configure your app, including the foxuser location.
>>
>>In terms of recording data paths and other user modifiable (sp?) info, use a system data table in your database. (that assumes an editable database) If the app is for lookup only (knowledge base of some sort) you may also want to consider using either system registry or an ini file. (I like ini files during preliminary distribution because they are more easily edited)
>>Use the Win32API function calls to read and write to registry and ini. (BTW, if you don't specify a drive the INI functions assume the ini file is in your system directory. That may be obvious to some, but it took me a while to figure that out.)
>>
>>HTH
>As far as I'm concerned, it doesn't need to modify the foxuser table. If I put foxuser on the CD, I have to SET RESOURCE OFF, right?
>
>I have seen here the woes some people have had trying to get around the setup wizard and use other setup programs. My related question is: can the runtime module, .dll files, and anything else that normally goes in the system directory possibly be put on that CD? The client is prepared for the possibility that it is not, but they sure would like to do so.
>
>Thanks, guys.


The only reason (that I can think of) why you would not be able to put
the *.dlls in the CD is if the CD was going to be written to..