How to split a replicated Access 97 database

Developers who are inexperienced with access databases often do not know that changing replication to object design, rather than data tables, can cause problems. This is disappointing, first of all, because replication seems to be the best way to distribute a complete access application, after all, Microsoft supports it.
The problem is that Jet replication is designed with data tables. This is because Jet replication is primarily used in Visual Basic applications where only data can be stored in *.mdb files. This is where it has been tested the most. For access 97来 says, it is always understood that a good developer always splits a database before converting it to a copy, so that only tables can be replicated. For the concept of splitting an Access database, see Chapter 15th, section 3rd, "Creating an application in Microsoft Access 97," which is available on the Access 97 CD.
Without splitting the database before copying, you will find that the size of your copy will "swell". This is because every change you make to a format or module, such as being placed in a hidden table, becomes the information that needs to be replicated. Imagine that you worked 30 times correctly to do a module's code work. These changes (with the exception of the last unwanted) are sent to all replicas, and the developer cannot split before replication encounters an annoying problem: After the replication is done correctly for a while (perhaps even months), the module suddenly fails, or the form cannot be opened.
So how can you split a database that has been replicated? I suggest you follow these steps here.
Do not use the Split Database Wizard. That's because it's just the wrong way to split the database so that your datasheet can't be copied---it moves the table to a new file, and put the rest of the object in the copy, and we have to do is to put the data table in the copy, and the other objects moved to the new copy of the database file. In that case, the rest of the backend can be copied, as part of the current replica setting, and the front-end is now a stand-alone database that can only be copied to every application user.
To make sure that your copy is synchronized, you need to know that if you damage the Design Master, you have updated the data.
Create a new Access database file, which will be on the front. According to the Microsoft example, you can add "_fe" to the initial database name, although it does not matter what you are calling.
Open this new file and enter all queries, forms, reports, macros, and modules from the Design Master. If you place the switch board where you can use the Switch manager control, you will also need to enter the Switch Board Item table.
If you have performed database security, you will lose the allowable settings in all objects entered or connected in steps 4th and 5th. So, open the Design Master and copy these allowable settings to the new file (that is, the front end).
Now you need to add code to the front end, which updates the local copy of the connection to the user. In the developer solution database, you will find help in doing this work. It appears as a sample database with Access 97. From the use multiple databases category, select Start Connection table.
Distribute front-end to all of your users. Remember that the file should not be replicated again. You just have to copy it for the person you need. Call your users to switch to use the front end.  When you're sure they're using the front end now, you can go ahead and convert the Design Master to Cheng (the next two steps) so that they synchronize the next time and their copy will turn into the back end. Material
Open the Design Master and delete all the objects you entered in step 4th.
Two times to compact the Design Master and then synchronize it with your other replicas.
Note: If you want to continue with the exact naming convention that Microsoft uses in its Split Database Wizard, you will have to rename your back-end copy by adding "_be" to its filename. The safest way to do this is to use the move Copy command in the Replication Manager.