Peter,
In addition to the other ideas that you already have.
I have been in a similar position and have found Winzip to be a great tool in sending the revised forms to the client.
My approach to the table structures is to do all changes in code, so get up to speed on ALTER TABLE commands. This keeps their DBC in sync with yours. At the same time that you do an alter table, recreate in code any views that rely on that base table.
I exclude all of the Reports and some of the Forms from the EXE, so in many situations I can meet their requests with a minimal amout of effort, and small email attachments.

>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.
>
>2) I did a form update and so I just sent them the revised form SCT & SCX files. Is that correct?
>
>3) For report updates - do I send both the FRT & FRX files?
>
>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??!!!)
>
>5) Should I send the DBC file? That doesn't have any file data in it correct?
>
>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?
>
>Thanks...