Split during developent or after?

[constableparks]

I am creating a database and have about a dozen tables, have a dozen forms, and another half dozen queries. I realized that I will need to split this database into FE/BE, but at what point in the process should I do it? Now or after I have finished creating all of the tables/forms/queries/reports?

I have more tables/forms/queries to create before I'm ready for any users. Does development slow down in a split database?

Probably should have asked this question before I started development...

 

[pbaldy]

Not a big deal, but I'd split now. There are little things that may work with a local table but won't with a linked table (opening a recordset using the wrong arguments comes to mind). If you wait, just make sure you test thoroughly before releasing.

 

[constableparks]

Thanks Paul. How does the Compact and Repair work for split databases? Is it only performing action against the FE or BE or both?

 

[pbaldy]

Whichever you perform it from, it only performs the action against that one.

 

[constableparks]

Thanks for the info Paul. I appreciate your help.

 

[pbaldy]

Happy to help!

 

[Mark_]

Just as a follow up for what has been posted, splitting early allows you as the developer to work on different modules (especially if you need to make different front ends for different positions) MUCH easier. This means instead of one file with potentially hundreds of procedures you won't be dealing with, you have smaller files that are much easier to maintain and debug.