>I have an app I am working on that I needed to get into the hands of the end user prior to completion....
>
>I used the SETUP WIZARD to create the distribution diskettes and used them at the clients office.
>
>The client has begun using the portions that are finished and installing data.
>
>Here is the question(s)....
>
>1) Is there a surefire - easy way to upgrade code at a clients office after the installation and use has begun? Obviously you can't use the SETUP WIZARD because that uses the DB files.

You could create a second setup without the DB. If the client has already installed the software, he then have all the runtimes installed. As long as you don't apply a new SP or distribute a new COM, you could distribute only the needed files without the setup.

>2) I did a form update and so I just sent them the revised form SCT & SCX files. Is that correct?

Correct.

>3) For report updates - do I send both the FRT & FRX files?

Yes.

>4) When I update the actual "code" of the main program, that compiles into the EXE... do I need to send anything else to the client other than the EXE for that to work (any additional files that I don't know what they do that are in the directory??!!!)

Just the EXE, as long as you don't modify a COM.

>5) Should I send the DBC file? That doesn't have any file data in it correct?

You should send the DBC only if you had made change to it (add a table/view, change the structure of a table/view, delete a table/view, modify a rule, etc.) NOte that you will need to send the updated table also, if applicable. In that case, you will need to write a conversion program that backup the old table, install the new one and transfer the data from the old one to the new one.

>6) If I make table structure changes - I need to write a program to update the table structure at the client to match - right? I would NOT send the file DBF or SCX, correct? Is this when I'd use the DBC file?

See my reply for item #5. You could either send the new table and transfer the data, or write a program that modify the structure of the table. If you send a new table, don't forget to send the DBC also, because it had change to reflect the new structure of the table.

HTH