 | |
Citrix Question Regarding Data Corruption
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: Citrix Question Regarding Data Corruption -
09-22-2010
, 02:59 PM
|
Do you have a setup where all users get their own copy of the front end? * That requirement does not go away just because you are using Citrix. This is what I asked the IT department to set up when the database was originally installed. I'm trying to ascertain if this actually happened. |
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
#12
| |||
| |||
|
|
Note that the Auto FE Updater works well with Terminal Server/Citrix. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files * updated seehttp://www.autofeupdater.com/ |
Citrix.
#13
| |||
| |||
|
|
On 22 Sep 2010 02:46:45 GMT, "David W. Fenton" NoEmail (AT) SeeSignature (DOT) invalid> wrote: That all depends on whether or not the Citrix server is set to terminate sessions when the connection drops. If so, it would be like killing Access in the middle of an operation, which could easily corrupt the back end if records were in the process of being edited. I disagree for two reasons 1) I would assume that if Citrix is terminating the session it would do a controlled shutdown of all apps using the session. Identical to someone logging off their system with the Access app still open. |
sessions. I wouldn't want it set to terminate the session on a
timeout. It's just a bad idea, and doesn't really address the
"people" problem that is involved.
Quote:
|
2) What do you mean by edited? If you mean the user has added a record and is updating some fields or just changing a record and updating some fields then being abruptly terminated at that point won't cause corruptions. This stated being where the record select graphic is a pencil. Now if you meant that brief moment in time when Access is actaully updating the database as you move to a new record, close the form or do docmd.runcommand accmdsaverecord then yes being abruptly terminated at that point would cause corruptions. |
mean that unbound apps have no benefit over bound apps at all, and
we all know that's just not true at all.
--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/
#14
| |||
| |||
|
|
Now if you meant that brief moment in time when Access is actaully updating the database as you move to a new record, close the form or do docmd.runcommand accmdsaverecord then yes being abruptly terminated at that point would cause corruptions. Er, I think that's absolutely wrong, Tony. If it weren't it would mean that unbound apps have no benefit over bound apps at all, and we all know that's just not true at all. |
think I've disagreed with you occasionally but not always.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
#15
| |||
| |||
|
|
On 23 Sep 2010 20:08:24 GMT, "David W. Fenton" NoEmail (AT) SeeSignature (DOT) invalid> wrote: Now if you meant that brief moment in time when Access is actaully updating the database as you move to a new record, close the form or do docmd.runcommand accmdsaverecord then yes being abruptly terminated at that point would cause corruptions. Er, I think that's absolutely wrong, Tony. If it weren't it would mean that unbound apps have no benefit over bound apps at all, and we all know that's just not true at all. No we don't know that. You have stated that a number of times and I think I've disagreed with you occasionally but not always. |
benefit over bound apps? I don't believe I've ever in any forum made
such a statement, ever. Please provide citations.
In general, I'm mostly against unbound apps, but they do offer the
possibility of greater control and enhanced concurrency, if you do
things right. My opposition to them is based not on what they offer
or not, but on whether it's practical or makes sense to go unbound
with Access. My opposition is almost always based on that fact that
you might as well not use Access if you're going unbound, not that
you can't actually gain the alleged benefits from going unbound.
If bound forms worked as you say, there wouldn't be any benefit
there at all in going unbound.
--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.