Splitting Database

J

Jake

When I try to split my existing database I get the error "Subscript out of
range". Does anyone know how I fix this error to split the DB?

John
 
J

John W. Vinson

When I try to split my existing database I get the error "Subscript out of
range". Does anyone know how I fix this error to split the DB?

John
Click to expand...

Compact and repair the database first, just in case it's corrupt.

It's also not essential to use the database splitter wizard. You can split the
database manually. To do so make *THREE* copies of the database: a backup in
case you make a mistake; the future frontend; and the future backend.

Rename the backend from mydata.mdb to mydata_BE.mdb. Open it and ruthlessly
delete ALL your forms, reports, macros and modules. Compact and repair to free
up the space that they occupied. Check that your relationships are correctly
set up and close it.

Then open the copy that is to become the frontend. Delete the Tables from the
tables window (leave everything else alone). You may need to delete the
"manyest" table first, and work up to the "one-est" table to avoid referential
integrity error messages. Then use File... Get External Data... Link to link
to the tables in mydata_BE.mdb. Compact and repair the database. Test, test,
test everything!!

Note that if you have a switchboard created by the switchboard wizard, you
should except the table named Switchboard; it must remain in the frontend.
 
A

a a r o n . k e m p f

splitting the database doesn't help anything.. except store duplicated
data

upsize to sql server and a lot of your problems just go away.. you can
add fields to a table (while everyone else is using it)

and you can create queries-- you can have multiple people writing
queries at the same time

if you would jsut upsize to ADP.

FIle, New, Project (existing data)
 
B

BruceM

If the tables are in the back end, splitting the database does not store
duplicated data. There may be duplication inherent in the design, but that
is a different matter.

message
 
A

aaron.kempf

yes, it does!!!

having frontend and backend and tempMDB -- it's all just a whole bunch
of redundancy that isn't necessary

anyone with a clue would move to the magic of Access Data Projcts
 
B

BruceM

There are data tables in the BE. The FE has links to those tables. There
is also a lock file (.ldb), which is not a data file (at least not in the
sense of storing data recorded by users).

Data are not duplicated in the FE links to the BE tables, any more than a
reflection is a duplicate of the person standing in front of the mirror.
The analogy may be imprecise, but the point remains.

yes, it does!!!

having frontend and backend and tempMDB -- it's all just a whole bunch
of redundancy that isn't necessary

anyone with a clue would move to the magic of Access Data Projcts
 
A

aaron.kempf

Data.. and Logic-- is duplicated.. because in order to change a
table-- you need to do it in 3 places

that is not efficient.

with ADP, you change a table-- while people are using it-- and it
doesn't cause downtime.
 
T

Tony Toews [MVP]

B

BruceM

You are doing it wrong, then. You are correct that people need to be out of
the database before you change the table design, but that has nothing to do
with duplication.

Data.. and Logic-- is duplicated.. because in order to change a
table-- you need to do it in 3 places

that is not efficient.

with ADP, you change a table-- while people are using it-- and it
doesn't cause downtime.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Split cells next to 1 cell 1
Active Content in this file is blocked issue 1
Getting This Unknown Error From Outlook! 1
Word VBA Copy Heading and Content 4
Subscript Out of Range 0
Subscript on a subscript (double subscript) 1
How to count the numbers in a Word document? 0
Splitting a Database 1

Top