Unable to split database 1

[Garryg]

I have created my first database in Access 2000 with some outside help and<br>
am happy with the results except for a couple of problems.<br>
<br>
I have installed it on the server (Novell)in my client's office. On three<br>
of the workstations it works fine although a little slow on 2 (these<br>
systems have 32MB RAM). On the fourth workstation, which is the newest (an<br>
HP with 64MB RAM running Windows98), I am not able to make additions to the<br>
main form without either switching from form view to design view and back<br>
to form view or selecting Print Preview and closing back to form view. All<br>
of these are running the code and data from one MDB file on the server.<br>
This same problem occurred on one workstation in my office. I cannot see<br>
any coorelation between the workstation in my office and the workstation in<br>
their office other than they are both running Windows98. However, one of<br>
the other work stations in their office (this one works okay) is also<br>
running Windows 98.<br>
<br>
My other problem is not being able to split the database. It starts the<br>
process but I get a &quot;Subscript out of Range&quot; error followed by &quot;Invalid<br>
procedure call or arguement&quot; message. It does create a be.MDB file and if I<br>
open that file it appears that all the records are there but if I delete<br>
that file I can still open the database from the original file and all the<br>
records are intact.<br>
<br>
Thanks in advance<br>
Garry

 

[elizabeth]

You don't need to use a wizard to split the database; it's easy to do it manually. Just create an new database and import all the objects except the tables: File/Get External Data/Import/etc. Then do a File/Get External Data/Link Tables/etc. If this works, your new database is the front end, the one you'd want to point everyone to. If it doesn't work, you may learn which object if any is causing the problem. Once you test the new db you can go back and delete all the non-table objects from the original database.<br>
<br>
When you import all your non-table objects, you may find your other problem disappears, as one of the ways you can sometimes fix a corrupt object is to export and re-import it.<br>
<br>
<br>

 

[Zelandakh]

For extra performance, take the new front end and copy it to the local machines and leave the back end (tables) on the network. It improves perf no end.

 

[elizabeth]

If your users don't all use the same drive letter to map to the back end, be sure to use the &quot;//&quot; name (somebody help - what is this called? a net use stmt?) instead of the drive letter when you link. If you've already mapped to a drive letter you can change it by using the Linked table Manager Add-in under the Tools menu.

 

[BGillum]

I believe that the '\\' method of referencing a network object is called the Universal Naming Convention (UNC).<br>
When using the Linked Table Manager, you can get the UNC in your links by going through Network Neighborhood to locate your b.e., instead of through a mapped drive.