Splitting A Database

[Guest]

I have a database that has been split into a front and a backend database for
a multi user environment. I needed to add an additional table and I could
not figure out how to add the new table to the backend, so I deleted the
links to the table, imported the tables into the front end again and then ran
the database split wizard again. After doing this I can no longer import
data to one of the original tables. I can only import to a table that has no
link to the backend. I have developed a system that will have 8 to 12 users
and I will be making continuos program updates in a developmental area and
moving those into the user area. I used the security wizard to set up
security and have been creating mde files for the users to connect to the
backend. Can anyone please offer suggestions on how to resolve my issue?

Thanks

 

[Guest]

You have the right idea splitting your data. The backend should be located
on your server and the front end on each of the workstations. Make sure that
the workstations have the same mapping to the server.
If you need to make changes to the data, just open the backend in Access as
you would the front end. You may have to kick everyone out if you are
altering a table in use. If you add a table, then just link to the new table
in your front end. You can have a copy of the front end on the server to
make changes. Then, when the changes are completed, create your mde and
distribute it to the workstations through manual copy or a .bat file attached
to an icon on the desktop.

Hope this helps.

 

[Guest]

But how do I resolve my issue where I am unable to load data into one of the
original tables after I split the database the second time? Or, what action
should I take to get everything back in sync? After I split the databse the
second time I am unable to load data into one of the original tables. Is
there a way to get everything back in Sync?

 

[Guest]

I would suggest creating a new/blank database and importing all your tables
into it. That is a great way to clean up data. Be sure to rename to your
old backend name so that the links are correct.

Hope this helps.

 

[Guest]

I've read all of these posts regarding splitting databases. My question is,
can both the front end and back end both live in the same folder on the same
server? I've split my database and my user who volunteered to be my "guinea
pig" can't open either file. I haven't read anything that addresses the
location of the files. Does anyone know?

 

[Rick Brandt]

I've read all of these posts regarding splitting databases. My
question is, can both the front end and back end both live in the
same folder on the same server? I've split my database and my user
who volunteered to be my "guinea pig" can't open either file. I
haven't read anything that addresses the location of the files.
Does anyone know?

The front end "can" be on the server, but you would lose some of the
performance benefits of splitting and since you want each user to have their
own copy of the front end you would still need multiple files on the server
(one for each user) so I don't see the point of doing that.

Please clarify "can't open either one". Do they get an error? Do they have
full network permissions ot the folder?