If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database Splitter
Hello all,
I created a database on a corporate server with 20 users, 4 tables, 30 forms (that contains simple code) and 20 queries. Size prior to split is 14 MB. After the split FE is 14MB and BE is 11 MB. Hopefully, I am done with modifications. From what I understand with FE/BE... I can leave both FE and BE on the server to help with corruption and I/O. I could also distribute the FE to each user and have them copy it to their desktop. (I found a demo to keep the FE's in synch when modifications are made at www.rogersaccesslibrary.com) Is this Database size normal? Is the FE too large to effectively distribute to the user's desktop? Also, how does the FE/BE help with I/O? The user's will open forms that will kick off a query and will return a few hundred records for them to work, but each record in the query will make a change in the table (click a check box or systematically write the date worked with the ON CURRENT event). Any assistance or insight would be very appreciated. David |
#2
|
|||
|
|||
Is this Database size normal?
Try compacting: Tools | Database Utilities | Compact Before compacting, consider turning off Name AutoCorrect boxes under: Tools | Options | General Explanation: http://members.iinet.net.au/~allenbrowne/bug-03.html Is the FE too large to effectively distribute to the user's desktop? No. Also, how does the FE/BE help with I/O? If each user has a copy of the front end on their local machine, network traffic is reduced, because the forms, code, graphics, ..., the entire interface does not need to travel across the network. ... systematically write the date worked with the ON CURRENT Why? Unless you need to record the fact that the user visited the record, dirtying it the instant that the user visits the record seems like a great deal of unnecessary alteration of the data. -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "David" wrote in message ... Hello all, I created a database on a corporate server with 20 users, 4 tables, 30 forms (that contains simple code) and 20 queries. Size prior to split is 14 MB. After the split FE is 14MB and BE is 11 MB. Hopefully, I am done with modifications. From what I understand with FE/BE... I can leave both FE and BE on the server to help with corruption and I/O. I could also distribute the FE to each user and have them copy it to their desktop. (I found a demo to keep the FE's in synch when modifications are made at www.rogersaccesslibrary.com) Is this Database size normal? Is the FE too large to effectively distribute to the user's desktop? Also, how does the FE/BE help with I/O? The user's will open forms that will kick off a query and will return a few hundred records for them to work, but each record in the query will make a change in the table (click a check box or systematically write the date worked with the ON CURRENT event). Any assistance or insight would be very appreciated. David |
#3
|
|||
|
|||
Thank you Mr. Browne,
The sizes are after compacting. I am reading about creating forms that will allow the user to build their own query criteria so I don't have to have so many forms and queries out there. I will move the code to insert the current date to after update event. How would I go about distributing the FE? I can't email it (firewall and size limits). Can the users go to the server and CNTL+C and then paste it on their own desktop? Thanks again, and I appreciate all of the time you spend on these boards. |
#4
|
|||
|
|||
If you want to reduce the size further, try creating a new (blank) database,
turning off Name AutoCorrect, and then importing everything. Chances are it will reduce the front end somewhat. Use the form's BeforeUpdate event, not AfterUpdate. No point dirtying the code again immediately after the record is saved. Regarding keeping the front ends up to date, Tony Toews has a FE Updater utility for that at: http://www.granite.ab.ca/accsmstr.htm -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "David" wrote in message ... Thank you Mr. Browne, The sizes are after compacting. I am reading about creating forms that will allow the user to build their own query criteria so I don't have to have so many forms and queries out there. I will move the code to insert the current date to after update event. How would I go about distributing the FE? I can't email it (firewall and size limits). Can the users go to the server and CNTL+C and then paste it on their own desktop? Thanks again, and I appreciate all of the time you spend on these boards. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Images in a database | Franz | General Discussion | 10 | October 7th, 2004 09:35 AM |
Database Window Gone | DaveB | General Discussion | 2 | July 29th, 2004 12:24 AM |
Database periodically needs rebuild and locks users out | spectrum | General Discussion | 2 | July 13th, 2004 06:24 PM |
Database Splitter | Steve | Database Design | 2 | June 10th, 2004 05:54 AM |