 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / New Users / December 2007Updating backend
I have a form sub form one to many, multi-user database. This will be split with the backend on a network server and front ends placed on a couple of desktops. My question is what happens when the server goes down say for routine maintenance. Does everything come to a screeching halt? Or are the user allowed to make their records and print reports, then run a update query to append the new records at a later time? Id would like to read an article or some type of info on this subject. Richard, I generally include a table in the database that has one or more program parameters that I set for the whole program (all users). One of these fields is a Yes/No field called: "InMaintenance". In my application front end, in the Splash screens timer event (interval usually set to 60000), I add some code to test to see whether the InMaintenance field is true. If so, I display a warning message to the user, and begin a count-down timer, usually giving the user 5 - 10 minutes to log off (I usually pop up the reminder about every 2 minutes and occassionally just open the timer window and leave it on screen so that they can see it counting down). When the timer reaches zero, I call a subroutine that loops through all of the open forms and closes them (usually after performing a frm.Undo operation to cancel any pending changes). Then, once the last form is closed, it quits the application. Although this can give you some upset users when the record they were on closes without being saved, but such is life. Then, I create a simple application that the network admin opens and runs whenever he/she is going to take down the server. It just runs an update query that changes the [InMaintenance] field to NOT [InMaintenance] for each of the databases I have running on that server. After they have rebooted, they run the same application again to Set InMaintenance to False HTH Dale >I have a form sub form one to many, multi-user database. This will be split > with the backend on a network server and front ends placed on a couple of [quoted text clipped - 5 lines] > article > or some type of info on this subject. Thanks for the reply Dale, do you know of any good source material for updating backends and maintenance? > Richard, > [quoted text clipped - 36 lines] > > article > > or some type of info on this subject. Richard, I've learned most of what I know through trial and error, and reading posts that interest me on the newsgroups. In my experience, the Access MVPs are amazing, and do a far better job than the MVPs for the other elements of Office. In many cases, you will see 2 or 3 Access MVPs chime in on a particular topic. On the other newsgroups, you are lucky to get one. If they see someone has already responded, you almost never get another response and usually end up having to repost your message if the first respondant doesn't answer your question. I sometimes just drop into the newsgroup to read MVP responses to see how they would tackle a particular problem. Dale  SignatureDon''t forget to rate the post if it was helpful! Email address is not valid. Please reply to newsgroup only. > Thanks for the reply Dale, > [quoted text clipped - 40 lines] > > > article > > > or some type of info on this subject. >I have a form sub form one to many, multi-user database. This will be split >with the backend on a network server and front ends placed on a couple of [quoted text clipped - 3 lines] >to append the new records at a later time? Id would like to read an article >or some type of info on this subject. If the backend is down, everything DOES come to a screeching halt; the frontend has just pointers to the tables, not the tables themselves, and if the pointer points to a table which isn't available, it won't work. It doesn't damage your database or the frontend, and all will be well when the server comes up. If you require 1440 minutes a day, 7 days a week, never interruptible service - get a SQL/Server farm with multiple servers in different geographical locations (regional power or communication outages), and hire a bunch of really really good database administrators. I'll ask my little sister (the bright one in the family) if she wants a new job. John W. Vinson [MVP] John, if the backend is down for maintenance, is it possible to use a locale (not on the server) copy of your database to allow for records and reporst to be generated? then simply apply a update query to update the backend? Sometime our server is down in the morning and our drivers have to make 7-8 records each and print a delivery report..not doing so in not an option.. > >I have a form sub form one to many, multi-user database. This will be split > >with the backend on a network server and front ends placed on a couple of [quoted text clipped - 18 lines] > > John W. Vinson [MVP] > John, > [quoted text clipped - 6 lines] > our server is down in the morning and our drivers have to make 7-8 records > each and print a delivery report..not doing so in not an option.. PMFJI ... In theory, yes, but it sounds like a maintenance overhead nightmare to me, especially if you have more than one copy. Can't you host on a more reliable server? If this is business-critical then you sound like you have a good case. Keith. www.keithwilby.com >John, > [quoted text clipped - 3 lines] >our server is down in the morning and our drivers have to make 7-8 records >each and print a delivery report..not doing so in not an option.. You need to discuss this issue with your IT department. If their maintenance schedule is making it impossible for your drivers to get their job done... they need to remember that the IT department is in the service of your company, not vice versa!!! But to answer your question... yes, you can use Replication instead of linking to the backend. Replication lets you have multiple backends on (disconnected or not permanently connected) machines, and synchronize them on demand or on a schedule. Replication is a complex process, bloats your database, and requires a good bit of care, but if you can't get your IT department's cooperation it may be your best bet. Download the replication FAQ at http://support.microsoft.com/kb/282977/en-us and study it carefully. If you do choose to replicate, it's VITAL that you: - Replicate ONLY the backend, not the forms or reports - Make a backup FIRST - Keep the Replication Master in a safe place, unused; all data operations should be done on a replica, not the design master - Study the FAQ carefully! John W. Vinson [MVP] Thank you gentleman for your answers, I see now that I was worrying about a non issue. > >John, > > [quoted text clipped - 27 lines] > > John W. Vinson [MVP] |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.