RexesOperator
Registered User.
- Local time
- , 22:34
- Joined
- Jul 15, 2006
- Messages
- 604
I have reached the point in the database development where it will be loaded onto a server.
What are the advantages/disadvantages of splitting the db to be/fe vs leaving it intact on the server?
The db is to used load five excel spreadsheets. Otherwise all activity (reports, forms etc) is confined to db itself. At most there will be four or five users. There are currently about 2500 "sites" (the last link in the relationship design: Company->Contact->Transactions->Sites). This will grow to about 4000 in the next few months (I will be adding some historical information). It is anticipated to grow at an average of 1000 transactions per year.
I will not be maintaining it.
What are the advantages/disadvantages of splitting the db to be/fe vs leaving it intact on the server?
The db is to used load five excel spreadsheets. Otherwise all activity (reports, forms etc) is confined to db itself. At most there will be four or five users. There are currently about 2500 "sites" (the last link in the relationship design: Company->Contact->Transactions->Sites). This will grow to about 4000 in the next few months (I will be adding some historical information). It is anticipated to grow at an average of 1000 transactions per year.
I will not be maintaining it.