Hello,
I have a large Access db (300 MB at least) which is located on server. It is called patients.mdb and it is a Access 2003 version. This db is used by 4 PCs:
1. PC i - Win XP - Office 2007
2. PC ii - Win XP - Office 2003
3. PC iii - Win XP - Office 2003
4. PC iiii - Win XP - Office 2003
On all these PCs there is one simple shortcut which opens patients.mdb on server.
This is the *current* condition of my db:
- it works very slow,
- it is huge and it takes a lot of space (300 MB),
- some users can't open db from shortcut from desktop, instead they have to open Access and than open db from shortcut.
This is what I wand in *future* for my db:
- to work much faster,
- to avoid error caused from opening db using Office 2003 and Office 2007 from two or more PCs,
- to decrease size of db,
- to avoid craching db and similar.
My question is how can I realize my *future* requests and what are your recommendations based on your experience.
Any help is appreciated and many thanks in advance for prompt reply!
Adi
I have a large Access db (300 MB at least) which is located on server. It is called patients.mdb and it is a Access 2003 version. This db is used by 4 PCs:
1. PC i - Win XP - Office 2007
2. PC ii - Win XP - Office 2003
3. PC iii - Win XP - Office 2003
4. PC iiii - Win XP - Office 2003
On all these PCs there is one simple shortcut which opens patients.mdb on server.
This is the *current* condition of my db:
- it works very slow,
- it is huge and it takes a lot of space (300 MB),
- some users can't open db from shortcut from desktop, instead they have to open Access and than open db from shortcut.
This is what I wand in *future* for my db:
- to work much faster,
- to avoid error caused from opening db using Office 2003 and Office 2007 from two or more PCs,
- to decrease size of db,
- to avoid craching db and similar.
My question is how can I realize my *future* requests and what are your recommendations based on your experience.
Any help is appreciated and many thanks in advance for prompt reply!
Adi