Question DB won't split

[theKruser]

I am, once again, begging for the help of the DB geniuses on this forum. I am trying to split my db and am getting the errors you see in the screen shots. Please help!

Thank you in advance.

 

[DCrake]

You seem to have errors in your front end files, Access attempts to debug them prior to splitting the database. Suggest you desing one of your modules and select Debug - Compile (Your database name)

This will pinpoint the errors for you, once completed you should be a ble to split it ok.

David

 

[GaryPanic]

I had a splitting problem
in the end I copied the tables in to a fresh D/b copied everything else into a another d/b then linked them this way -

 

[theKruser]

You seem to have errors in your front end files, Access attempts to debug them prior to splitting the database. Suggest you desing one of your modules and select Debug - Compile (Your database name)

This will pinpoint the errors for you, once completed you should be a ble to split it ok.

David

I have no idea how to accomplish this. Can you help me? I would appreciate it very much.

 

[gemma-the-husky]

effectively all you need to do is copy the database (normal windows copy)

decide which tables you want in your backend - there may be some that you need to keep in the front end

delete or rename the backend tables in your front end (so effectively your dbs would now report these tables as missing)

then use file/getexternaldata/linktables to locate the backend (other copy of the database) and link the tables - now your dbs finds the tables again, but this time its tables in the back end, identified by a little arrow

afterwards you can tidy this up, by deleting the bits in each half of the database that are now unneddede, but you dont have to do this - i n fact it's probably better not to do so, until you are happy with what you have just achieved

job done

this really is a 2 minute job

--------
lots of utilities here to automate the process of connecting the back end, (mainly for the ease of your users - but all they do is connect as shown above)

 

[MSAccessRookie]

You seem to have errors in your front end files, Access attempts to debug them prior to splitting the database. Suggest you desing one of your modules and select Debug - Compile (Your database name)

This will pinpoint the errors for you, once completed you should be a ble to split it ok.

David

DCrake is absolutely correct here. The errors that your attachments show indicate that there is a problem in the present application. While it is true that moving the tables to an empty database and linking to them will effectively create the split database that you are looking to get, it is also true that it will propogate the error that you currently have. What DCrake is suggesting may not be the easiest solution, but it is probably the best for the long run.

Use the Tools/Macros/Visual Basic Editor Menu Option to open the VB Editor. You can also select any Form (preferably one that uses VB Procedures or Functions), place it into Design Mode, and open the Visual Basic Editor using the properties form.

Once the Visual Basic Editor has been opened, select Debug/Compile (Your database name), and Access will show you anything it considers to be an unrepaired error. Fix the errors and then try the split again.

 

[Pat Hartman]

I got the subscript out of range error when upsizing a table to SQL Server and the problem was a date that was valid as far a Jet was concerned but was out of the range that SQL server allows for SmallDateTime which is what Access dateTime fields upsize to. The problem date was a typo of course and fixing it solved the problem. Since you are not upsizing, I don't know what might cause the problem.

I would run the split one table at a time to see what table was causing the problem. Once I identified the table, I would examine the table data by sorting ascending and then descending on each column of the table so I could see what type of data was contained. You can also try exporting the problem table to a .csv file and that should get rid of any corruption in the table. You can then link to the .csv file and append it to an empty copy of the table. This will preserve any autonumber values.