Access Violation on Save in EssentialPIM 1.82 Free (W2K SP4)

Support related problems and questions

Moderators: Max, TerryRogers

Post Reply
gippledocks
Posts: 3
Joined: Fri Aug 25, 2006 7:41 am

Access Violation on Save in EssentialPIM 1.82 Free (W2K SP4)

Post by gippledocks »

First let me say that I'm very impressed with EssentialPIM for its simplicity, efficiency and general lack of bloat.

Unfortunately I'm affected by a problem. It doesn't damage data or stop me working but it is inconvenient.

I'm running EssentialPIM 1.82 Free under Windows 2000 SP4 with all MS patches to date. I'm running under a local user account that is a member only of the Users group (i.e. not a member of Administrators).

When saving (regardless of whether manual, automatic or save on exit) from the Notes view with any of certain specific notes active I get

"Access violation at address 006585FB in module 'EssentialPIM.exe'. Write of address 00000036."

Despite the error, the data seem to be saved intact.

As I say, certain specific notes always give this error. Other notes do not.

If I save from any view other than Notes, I can save without error.

I've tried compressing the database but the problem persisted unchanged afterwards.

To aid diagnosis I'm happy to send provide my .epim file (with details of which notes give the error) and EPIM.ini privately, though I prefer not to attach them to this post.
gippledocks
Posts: 3
Joined: Fri Aug 25, 2006 7:41 am

Post by gippledocks »

I have just noticed that notes that produce the problem on Save also produce the identical error message on Print Preview.

I should be grateful for a solution.
Max
Site Admin
Posts: 21714
Joined: Wed Dec 08, 2004 11:39 pm
Has thanked: 819 times
Been thanked: 364 times
Contact:

Post by Max »

Hello,

thank you for the report!

Yes, we need to reproduce the problem on our machines to be able to fix it.
You can make a copy of your database (Save As), then remove all irrelevant data and send it to me to ma@essentialpim.com please, with a link to this post.
What I suspect though, it is a bug persistant only on Windows 2000 machines. That's one of the reasons we officially do not support Windows 2000 platform...
Last edited by Max on Sat Aug 26, 2006 2:19 pm, edited 1 time in total.
Maxim,
EPIM Team
Post Reply