>When I run a setup wizard, I didn't have a table in my project cause I want my users to access the central table. But it includes the table anyway.
>
>And my user will enter data to the table on their workstation not on the server.
>
>What do you recommend to do?
>

Rather than including the tables/databases in the project itself, I prefer to run something similar to GENDBC (I use a commercial product called SDT) that builds the empty tables/database container/views/indexes on site during the install process (I run the equivalent of a post-setup executable as a part of my workstation configuration install; this builds the CONFIG.FPW for the station, sets up local directories, shortcuts and the like for the workstation.)

SDT provides mechanisms to do this and much more; if you have not finalized how you're going to handle data distribution and maintenance, I'd seriously consider buying it. it has very reliable mechanisms for reidexing, packing, and in some cases, even repairing some types of data corruption. It also provides a very strong mechanism to update database containers, table structures, indexes and views for systems that have already been deployed. It's saved me many times the initial cost of purchase. Stonefield is a member of the UT Partnership Program, and offers a discount to PUTM members; the discount on SDT alone about covers the cost of a year's PUTM subscription here.

>Thanks everyone.
>
>Angela:)