In network approach, use Split database or one file with shortcut to every client?
Hi:
Which is better to do , when I need to deploy a small application on a network!
1- Split my ms app. To front and back end, put the back end in the server and then link all clients to it.
2- Without splitting the ms app. , just put the app file in the server, and take a shortcut to every client.
Please help
Which is better to do , when I need to deploy a small application on a network!
1- Split my ms app. To front and back end, put the back end in the server and then link all clients to it.
2- Without splitting the ms app. , just put the app file in the server, and take a shortcut to every client.
Please help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
#1, #1, and #1
Jim.
Any and all cases ... Split, each user separate copy of FE. Period.
mx
mx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
#4, great point
trailer...
Access db size limit is 2GB, so with one db, this is your hard limit.
With a very basic split db, you at least then have 4GB
Access db size limit is 2GB, so with one db, this is your hard limit.
With a very basic split db, you at least then have 4GB
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you very much for participate
In a nutshell:
Split the DB
Front end MDB (accde) on each users workstation.
Linked into one single back end db on a server...