Is there any way to force data entires to be saved immediately, without closing the form on which they're made, so that these changes can be reflected across a network? My problem is that my users often leave a particular form open as they periodically add data to it over a period of 20-30 minutes. Some of that info is used to update a tracking module elsewhere in the database, but none of those updates are available until the user closes the form. I've tried putting me.dirty = false in the after update event of each control (as I've seen mentioned elsewhere) but that does nothing. I suppose I could force the form closed with a timer event, but that may cause people to lose data. -- Message posted via http://www.accessmonster.com
hi, vircalendar via AccessMonster.com wrote: > Is there any way to force data entires to be saved immediately, without > closing the form on which they're made, so that these changes can be > reflected across a network? What kind of application architecture do you have (FE/BE)? > I've tried > putting me.dirty = false in the after update event of each control (as I've > seen mentioned elsewhere) but that does nothing. Saving the data in the after update event of each control is not always possible, as the data may violate some constraints. > I suppose I could force the form closed with a timer event, but that may cause people to lose data. Use the form timer to save the changes periodically using Dirty = False. Add an appropriate error handler. You only "loose" data if it cannot be saved due to constraint violation. mfG --> stefan <--
At the moment, the DB is not split and it's being accessed across an intranet. I will be spliiting to BE on a server and FE on individual workstations once I finish ironing out bugs like this one. I hesitate to split it before then because I don't want to have to individually update the satellite computers more than necessary. What sort of constraints are you talking about? The data I want to save as it comes in are time fields that are updated by code when the user double- clicks on the control. I would like those times to be saved as soon as they are entered, so they can be accessed by other parts of the DB even if the form stays open. When you refer to the timer, are you saying that dirty=false with the on timer event should refer to the entire form and that this would be better than having the dirty=false code added to the individual controls? Stefan Hoffmann wrote: >hi, > >> Is there any way to force data entires to be saved immediately, without >> closing the form on which they're made, so that these changes can be >> reflected across a network? >What kind of application architecture do you have (FE/BE)? > >> I've tried >> putting me.dirty = false in the after update event of each control (as I've >> seen mentioned elsewhere) but that does nothing. >Saving the data in the after update event of each control is not always >possible, as the data may violate some constraints. > >> I suppose I could force the form closed with a timer event, but that may cause people to lose data. >Use the form timer to save the changes periodically using Dirty = False. >Add an appropriate error handler. You only "loose" data if it cannot be >saved due to constraint violation. > >mfG >--> stefan <-- -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200703/1
"vircalendar via AccessMonster.com" <u4313@uwe> wrote: >At the moment, the DB is not split and it's being accessed across an intranet. >I will be spliiting to BE on a server and FE on individual workstations once >I finish ironing out bugs like this one. I hesitate to split it before then >because I don't want to have to individually update the satellite computers >more than necessary. Split it now. However you really want to put the FE on each machine or place in a user specific directory on the server. This will help avoid some weird error messages when users are changing the same forms record source, filters and such as well as corruptions. It is also much easier to implement a new version of the database with changed queries, forms, reports and VBA code. I specifically created the Auto FE Updater utility so that I could make changes to the FE MDE as often as I wanted and be quite confident that the next time someone went to run the app that it would pull in the latest version. For more info on the errors or the Auto FE Updater utility see the free Auto FE Updater utility at http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up to date. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm
"vircalendar via AccessMonster.com" <u4313@uwe> wrote: >My problem is that my users often leave a particular form open as they >periodically add data to it over a period of 20-30 minutes. Some of that info >is used to update a tracking module elsewhere in the database, but none of >those updates are available until the user closes the form. I've tried >putting me.dirty = false in the after update event of each control (as I've >seen mentioned elsewhere) but that does nothing. Just off hand, without doing any testing, that should've worked. So I'm a bit puzzled. > suppose I could force the >form closed with a timer event, but that may cause people to lose data. Agreed. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm
"vircalendar via AccessMonster.com" <u4313@uwe> wrote > At the moment, the DB is not split and it's being > accessed across an intranet. I will be spliiting to > BE on a server and FE on individual workstations > once I finish ironing out bugs like this one. I > hesitate to split it before then because I don't want > to have to individually update the satellite computers > more than necessary. See my article on "versioning" at http://accdevel.tripod.com and look for MVP Tony Toews' "Auto FE Updater" at his http://www.granite.ab.ca/accsmstr.htm site (which is chock-full of other good information, also). What you seem to view as an intimidating task is No Big Deal, in actual fact. Larry Linson Microsoft Access MVP
Thanks. Larry Linson wrote: > > At the moment, the DB is not split and it's being > > accessed across an intranet. I will be spliiting to >[quoted text clipped - 3 lines] > > to have to individually update the satellite computers > > more than necessary. > >See my article on "versioning" at http://accdevel.tripod.com and look for >MVP Tony Toews' "Auto FE Updater" at his >http://www.granite.ab.ca/accsmstr.htm site (which is chock-full of other >good information, also). What you seem to view as an intimidating task is No >Big Deal, in actual fact. > > Larry Linson > Microsoft Access MVP -- Message posted via http://www.accessmonster.com
