Module Visibility

lameduck · Post by **lameduck** » Fri Apr 03, 2009 7:04 am

Thank you for allowing user choice which modules a visible when you start up EPIM. However, this is not database dependent, which means the freedom you give the user is immediately limited.

Can we please have, database dependent module visibility?

Max · Post by **Max** » Fri Apr 03, 2009 7:48 am

What do you mean by "Database dependant" and how namely is "freedom you give the user is immediately limited"?

lameduck · Post by **lameduck** » Fri Apr 03, 2009 8:04 am

What do you mean by "Database dependant"

For example if I wish to see notes and schedule on database "A"; and I wish to see ToDo, Mail and Contacts only in database "B". I can't do that! Can I?

how namely is "freedom you give the user is immediately limited"?

You give a choice to chose but it can't be set for each database - Thats limited?

Max · Post by **Max** » Fri Apr 03, 2009 8:16 am

You are right, this setting is stored in EPIM Configuration file, not in Database.
Suggestion noted, but do not see a big need so far at least.

lameduck · Post by **lameduck** » Wed Apr 29, 2009 4:18 am

Ok, I have more information to share to get this issue resolved because BETA 3 does not open on my XP (Revision 2) system and it is similar to the error message in this thread: viewtopic.php?f=2&t=7089.

Towards solution, firstly, this is the error message that XP prepares when EPIM crashes:

szAppName : EssentialPIM.exe szAppVer : 3.0.0.0 szModName : hungapp
szModVer : 0.0.0.0 offset : 00000000

C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WEReb93.dir00\EssentialPIM.exe.mdmp
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WEReb93.dir00\appcompat.txt

Secondly, if you take the V2.8.1 Portable and unzip it and copy the V3.Beta exe into that environment then EPIM V3.BETA opens up as it should. This should point to errors somewhere in the coding - surely???

Of course, it opens the software, and can create a new database, but cannot open an old database as the previous version dll's do not accommodate the V3 table structures. The error message is that the software expects "x" number of tables, but has found "X" tables in database. I'm not a developer, but logically, this would point to a coding error in how EPIM V3 dll's engage XP runtime files. It is not however up to me to solve the problem - my knowledge does not extend that far.

Any ideas???

lameduck · Post by **lameduck** » Wed Apr 29, 2009 10:05 pm

Please disregard this post. I posted in error in the wrong thread. This query is now at viewtopic.php?f=2&t=7056

EssentialPIM