From: dpb on 31 Jan 2010 10:34
Tony Toews [MVP] wrote:
> "Helmut Meukel" <NoSpam(a)NoProvider.de> wrote:
>> He phoned me and we fixed it by opening the file in the morning and
>> closing it when the app was shut-down at the end of the second shift.
>> I wasn't happy with this 'fix' but we had never since problems with the
> My concern there would be that if the system or your app failed you
> would likely loose the entire contents of the log file.
> I wonder if a log file per day would be a better solution and opening
> and closing it for each entry would've worked as the daily log file
> would be much smaller.
It would seem two shifts would be less than a day already... :)
Possibly in this case granularity could be on a per PLC and perhaps per
hour and minimize potential loss w/o growing the file size excessively.
Wonder if the problem also wasn't actually a depth of the directory
rather than file size.
From: Tony Toews [MVP] on 31 Jan 2010 15:34
"Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote:
>My concern there would be that if the system or your app failed you
>would likely loose the entire contents of the log file.
Actually you could lose everything since the last time you closed the
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/
Granite Fleet Manager http://www.granitefleet.com/