Adding Forms in a split DB

[Homegrownandy]

I split my DB a few weeks ago and I struggled to get any new forms working after I did so.

What's the standard way to make new forms in a split DB? do you make them in the back end then move them over?

My database isn't split anymore because of this issue, but as more users need to use it. its becoming important to have it split.



Thanks.

[ItsMe]

You should have a master copy of the FE stored somewhere safe. When you want to create a new version, copy the master. After you are finished developing a new version, replace the master.

Distribute copies of the master to the users.

[Homegrownandy]

I see, but when I made forms on the front end last time it just didn't work. (doing it the same as I do when its not split)

[JamesDeckert]

There should be very little difference after the split. The tables are now linked instead of local, but when you make a new form, the form doesn't know the difference. All your forms/queries/reports/code are created on your front end and the data resides in the back end. It is still possible to have tables in the front end if they contain temporary data. This front end is copied to other computers when you want to share the program. Relinking of the backend tables may need to happen depending on if the path to the shared drive where the back end resides is the same.

[Homegrownandy]

So you would make a form using the form wizard on the front end?

Ill have more details when I do actually split it again. Last time nothing was appearing correctly in the wizard.
I still kept the front end on the network drive last time I did it. But issuing it is defiantly a good idea.

[JamesDeckert]

>>So you would make a form using the form wizard on the front end?
yes
a copy of the Front end should be on each users local drive. Only the back end is shared

[Homegrownandy]

Thanks guys.