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
|
|||
|
|||
Now I have split....
I'm not sure if I should start a new thread here - but the last one went a
bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... |
#2
|
|||
|
|||
You will keep a master copy of the front-end. As you make changes to it,
you will redistribute the new front-end to your users. Personally, I have a version table on my back-end and a one on my front-end. If I want to distribute a new copy, I change the version date in my back-end to the current date. I also set the date on the version table in my front-end copy on the LAN to today's date. Each of my user's open the front-end on their PCs and code runs that checks the version in their local table against the version in the back-end table. If they don't match, then a batch job runs that deletes their local front-end and copies the LAN front-end. There are lots of ways to automate the update process, this is just one method. You could simply email your users and say, "Hey, there is a new version of the database on the LAN. Copy it to your harddrive and start using it." Search previous posts in the newsgroups to find other ways to handle this. Tony Tawes (sp?) has a tool called auto-updater. You could try to search for that. ** Mkae sure you kee at least one good copy of the front-end handy when you go to make changes. I keep bakups of almost all versions of my front-end on a ZIP disk in case I ever need to fall back. I put them there before I start making changes. Good Luck, Rick B "HelenJ" wrote in message ... I'm not sure if I should start a new thread here - but the last one went a bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... |
#3
|
|||
|
|||
You give each user his/her own copy of the front end file. The back end file
is put on a network server in a shared folder. All users must have read/write/create/delete privileges on that shared folder. The front end must be linked to the tables in the back end using the location of the back end file. There is code available that enables your front end to automatically restore links to the backend. See The ACCESS Web: http://www.mvps.org/access/tables/tbl0009.htm I personally use a function that I wrote that uses a table in the front end (I store various paths to link to the back end in that table, each is prioritized so that I can use the front end for development and for distribution without having to keep changing paths in the table) to get the path, and then to relink to the tables. -- Ken Snell MS ACCESS MVP "HelenJ" wrote in message ... I'm not sure if I should start a new thread here - but the last one went a bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... |
#4
|
|||
|
|||
Sorry for the OT in the last post. I shall try to make amends...
The FE can be installed on each workstation OR accessed from a single file on a server OR you can have a directory on the server for each user and have a separate FE in each. I have done all of these. There are advantages and disadvantages to each. * FE on the Server: - Advantage: one copy to maintain (you should do your development in an off-line copy and copy it over the network version) - Disadvantages: 1) it is more susceptible to corruption. 2) performance suffers some. 3) you have to kick everyone out of the application in order to copy your revised version over it. 4) may have multi-user problems if you create temporary tables and such. * Separate FE in separated directories on the server: - Advantage: 1) no multi-user issues. 2) less danger of corruption - Disadvantages: 1) performance can suffer. 2) you have to copy your development copy over each individual copy. 3) you have to kick the user out in order to over-write it. * FE on each workstation: - Advantages: 1) no multi-user issues. 2) less danger of corruption. 3) improved performance (over the other options) - Disadvantages: 1) you have to manage updating the FE on separate systems. The normal recommendation is to put the FE on each workstation and I generally agree with that. This does require some sort of update routine when you change the application. On my website (www.rogersaccesslibrary.com) there is a small sample database called "KeepingDatabasesInSync2.mdb" that does this. Tony Toews has a utility called "Auto FE Updater" (http://www.granite.ab.ca/access/downloadsindex.htm) that also does this. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "HelenJ" wrote in message ... I'm not sure if I should start a new thread here - but the last one went a bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... |
#5
|
|||
|
|||
"Roger Carlson" wrote:
Sorry for the OT in the last post. I shall try to make amends... The FE can be installed on each workstation OR accessed from a single file on a server OR you can have a directory on the server for each user and have a separate FE in each. I have done all of these. There are advantages and disadvantages to each. * FE on the Server: - Advantage: one copy to maintain (you should do your development in an off-line copy and copy it over the network version) - Disadvantages: 1) it is more susceptible to corruption. 2) performance suffers some. 3) you have to kick everyone out of the application in order to copy your revised version over it. 4) may have multi-user problems if you create temporary tables and such. * Separate FE in separated directories on the server: - Advantage: 1) no multi-user issues. 2) less danger of corruption - Disadvantages: 1) performance can suffer. 2) you have to copy your development copy over each individual copy. 3) you have to kick the user out in order to over-write it. * FE on each workstation: - Advantages: 1) no multi-user issues. 2) less danger of corruption. 3) improved performance (over the other options) - Disadvantages: 1) you have to manage updating the FE on separate systems. The normal recommendation is to put the FE on each workstation and I generally agree with that. This does require some sort of update routine when you change the application. On my website (www.rogersaccesslibrary.com) there is a small sample database called "KeepingDatabasesInSync2.mdb" that does this. Tony Toews has a utility called "Auto FE Updater" (http://www.granite.ab.ca/access/downloadsindex.htm) that also does this. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "HelenJ" wrote in message ... I'm not sure if I should start a new thread here - but the last one went a bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... Thanks for all your helpful advice and don't worry about the "OT" - when developing in Access I think you need a sense of humour :-) Just at the moment I feel as though I am standing on the edge of a large pit full of all kinds of "stuff" about Access that I really don't understand - at the moment I can still breath - but I haven't really taken the plunge (I did make a change to my references library yesterday - eek!) Is there any book series of books that any of you could recommend - I have an Access Bible and even a VAB for Dummies - both of which have helped - but now I feel I need something that bridges the gap between what is, if you like "inside" Access eg tables and even a little code - and the link to the outside world - I don't even really know what it is I am looking for - but any advice gratefully recieved - this Discussion group really is a life line! |
#6
|
|||
|
|||
Is there any book series of books that any of you could recommend - I have
an Access Bible and even a VAB for Dummies - both of which have helped - but now I feel I need something that bridges the gap between what is, if you like "inside" Access eg tables and even a little code - and the link to the outside world - I don't even really know what it is I am looking for - but any advice gratefully recieved - this Discussion group really is a life line! Helen, Let me suggest that you take a look at the list in the link below. It is Jeff Conrad's big list of Access references. It has more than you will ever need. www.ltcomputerdesigns.com/JCReferences.html -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html |
#7
|
|||
|
|||
You might also want to look at the Recommeded Reading page on my site.
(http://www.rogersaccesslibrary.com/l...edreading.html) I highly recommend all of them. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "HelenJ" wrote in message ... "Roger Carlson" wrote: Sorry for the OT in the last post. I shall try to make amends... The FE can be installed on each workstation OR accessed from a single file on a server OR you can have a directory on the server for each user and have a separate FE in each. I have done all of these. There are advantages and disadvantages to each. * FE on the Server: - Advantage: one copy to maintain (you should do your development in an off-line copy and copy it over the network version) - Disadvantages: 1) it is more susceptible to corruption. 2) performance suffers some. 3) you have to kick everyone out of the application in order to copy your revised version over it. 4) may have multi-user problems if you create temporary tables and such. * Separate FE in separated directories on the server: - Advantage: 1) no multi-user issues. 2) less danger of corruption - Disadvantages: 1) performance can suffer. 2) you have to copy your development copy over each individual copy. 3) you have to kick the user out in order to over-write it. * FE on each workstation: - Advantages: 1) no multi-user issues. 2) less danger of corruption. 3) improved performance (over the other options) - Disadvantages: 1) you have to manage updating the FE on separate systems. The normal recommendation is to put the FE on each workstation and I generally agree with that. This does require some sort of update routine when you change the application. On my website (www.rogersaccesslibrary.com) there is a small sample database called "KeepingDatabasesInSync2.mdb" that does this. Tony Toews has a utility called "Auto FE Updater" (http://www.granite.ab.ca/access/downloadsindex.htm) that also does this. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "HelenJ" wrote in message ... I'm not sure if I should start a new thread here - but the last one went a bit off topic so... OK I have now split my database, (well only on my system) - but doesn't this now mean more work for me? from the articals that I read I got the impression that the front end has to be "installed" on each users PC - so won't that mean when I develop new reports forms etc I will have to copy it into multiple database front ends? (currently only 2 but will become more) Or do I install the front end on the server so the users open it from there? Sorry I'm slightly confused and all the articles that I read seem to only ever give part of the picture... Thanks for all your helpful advice and don't worry about the "OT" - when developing in Access I think you need a sense of humour :-) Just at the moment I feel as though I am standing on the edge of a large pit full of all kinds of "stuff" about Access that I really don't understand - at the moment I can still breath - but I haven't really taken the plunge (I did make a change to my references library yesterday - eek!) Is there any book series of books that any of you could recommend - I have an Access Bible and even a VAB for Dummies - both of which have helped - but now I feel I need something that bridges the gap between what is, if you like "inside" Access eg tables and even a little code - and the link to the outside world - I don't even really know what it is I am looking for - but any advice gratefully recieved - this Discussion group really is a life line! |
#8
|
|||
|
|||
Thanks to you both - if I read all that it should keep me quiet for a while :-)
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Split text cell into seperate colums without splitting up a word | kevin_frisch | General Discussion | 1 | November 5th, 2004 09:03 PM |
split map | xxx | General Discussion | 1 | November 4th, 2004 12:23 AM |
change database from a split to not split | Joel | Database Design | 3 | July 14th, 2004 05:49 PM |
Using Split function in a query. | Randal | Running & Setting Up Queries | 2 | June 11th, 2004 04:22 PM |
split worksheet | patrick072040 | Worksheet Functions | 3 | September 15th, 2003 01:00 PM |