change database from a split to not split

[Joel]

I split my database but know we need to put it back to what it originaly was.

How do you do it?

I deleted all the split tables and then imported the tables back but know it accesses the tables very slow. What did I do wrong?

 

[Lynn Trapp]

Why did you think you needed to put it back to a single file, rather than
leave it split? Is everyone now accessing the same single file stored on a
network? If so, then that is probably the cause of your performance hit.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

I split my database but know we need to put it back to what it originaly was.

How do you do it?

I deleted all the split tables and then imported the tables back but know

it accesses the tables very slow. What did I do wrong?

 

[Lynn Trapp]

Joel,
It sounds like you already know how to unsplit the database and that your
performance problems got worse when you did so. Let me suggest that you take
a look at Tony Toews' website to see if you can see something there that
might be causing your slow performance.

http://www.granite.ab.ca/access/performancefaq.htm

One of the things that I would point out is that Tony, and all MVP's, will
ALWAYS recommend that you work from a split database, despite the problems
in updating the frontend to individual computers. If your performance
problem is connected with the splitting of the database, it is likely due to
the lack of a persistent connection, which Tony covers on his website.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

Thanks for your thoughts

Before I split the data base we had very good performance accross the

network from one large database. After I did the split it take a long time
to access any information. Plus it gets confusing when doing updates to
each workstation for the main forms.