"David W. Fenton" wrote:[color=blue]
> "Albert D.Kallal" <PleaseNOOOsPAMmkallal@msn.com> wrote in
> news:Owy1H#qdFHA.3032@TK2MSFTNGP10.phx.gbl:
>
> >> Keep in mind this is all run on Citrix Metaframe
> Presentation
> >> Server 3.0 and the whole shabang runs on the server
> itselfl; the
> >> front ends and back end. Each user has their own
> front end.[color=green]
> >
> > Yes, clear on the above....
> >
> > The interesting issue here is that 'all of a sudden' seems[/color]
> to be[color=green]
> > the strange part. That seems strange if no updates or[/color]
> anything was[color=green]
> > done, and the behavior started to change. I have to think[/color]
> somthing[color=green]
> > happend here.....[/color]
>
> It sounds like some kind of patch or hotfix was applied to the
> server.
>
> I've told this story a gazillion times, but it teaches a good
> lesson, so I'll tell it again:
>
> Back in winter of 1999 a client of mine was was using a nice
> app of
> mine that had a replicated back end to support their two
> offices and
> two off-site users. Everything regarding replication had been
> working smoothly for about 9 months when suddenly one day at
> 2:30pm
> the back end in the NYC office reported itself corrupted. When
> we
> compacted a copy, it came up having lost replicability.
>
> We did troubleshooting on this for quite some time, recovering
> manually the data that had been entered since the last
> successful
> synchronization (it was on a schedule for several times a day,
> so it
> wasn't a huge number of updates; and all the data tables had
> time
> stamps in them, so I know what had been updated when).
>
> Eventually, we determined that a hotfix that had been applied
> to
> Exchange Server (to fix the problem with Exchange not shutting
> down
> when the server was shut down, and causing the server to shut
> down
> dirty) about 15 minutes before the first corruption. Since the
> machine should never have had Exchange Server running on it in
> the
> first place, we backed out the hotfix.
>
> The problems vanished and never returned.
>
> Now, this was a case where two interesting things happened:
>
> 1. a patch to an unrelated piece of software caused corruption
> of an
> Access database, and
>
> 2. the consultants involved were too stupid to ask if Exchange
> Server was in use. Had they done so, they could have saved
> everybody
> a lot of grief by simply shutting down Exchange Server instead
> of
> applying a hotfix for a program that wasn't even in use.
>
> So, I'd try to determine exactly when the problem first
> started
> occurring, then go back to the event logs to see if there's
> anything
> there. Hopefully they are configured to not overwrite too
> quickly
> and you could find out what happened from them.
>
> --
> David W. Fenton
>
http://www.bway.net/~dfenton
> dfenton at bway dot net
>
http://www.bway.net/~dfassoc[/color]
Each user has their own front.
The frequency of the problem in the last month or so is -
File Size - Date - Time
696,368 25 May 15:32
941,668 27 May 16:03
625,604 13 Jun 20:48
974,596 21 Jun 12:48
-----------------
Normal file size is 27,984 or so.
I had seen this occur at least two times in the last 12 months besides
this past 30 days.
-------------------
I know what you are saying about updates and hotfixes, its too bad
that the timeline doesnt match up with any server work.
Thanks everyone for your input,
Jameso321
--
Posted using the
http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL:
http://www.dbforumz.com/MS-Access-DB...ict234126.html
Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.dbforumz.com/eform.php?p=812499 
