VSDK.framwork conflict?

[Ruslan Zasukhin]

On 1/13/10 7:44 PM, "Tiemo Hollmann TB" <toolbook at kestner.de> wrote:

Hi Tiemo,

> I have an Rev App with a V4REV_3 DB, which is read only.

APP is read only... OR DB is read only?
HOW YOU KNOW this?

Your db files marked as read-only?

 
> Now I have always again customers, where my App has run fine (on Mac and
> Win, different versions) and from one day to the other they can't run my app
> anymore because the DB can't be opened or read anymore.
> 
> At some customers the problem stays also after a couple of restarts of my
> app, reboots of the computer. Some customers get it run again after a
> restart, but the error cames back again another time. At some customers
> after a fresh reinstall the app runs again, but there are also customers
> where the same error comes up even after a complete reinstall of the app.
> 
> Because of my app has run and nothing has changed in my app or the db, I am
> thinking of any conflicts with the system. E.g. could it be that the
> VSDK.framework on Mac can produce any incompatibility or conflicts? Is this
> possible? Or any other component? What about a conflict of the dlls on
> windows?

No.

 
> Could it be a conflict of different versions of the VSDK.framework on the
> same machine? What the heck is the VSDK.framework at all?

This is the hole Valentina engine v1.

You or your users have other copies of VSDK.framework??
Then we talk about MACs ...
 

> Does Valentina writes when starting any components to any directories, which
> could get corrupted, where I could look for or delete them, so that they
> would be recreated?

No.

Only dbname_xx.tmp when you open some db into OS/tmp folder
 
> Any other idea, what could produce such conflicts that the valentina db
> can't get opened any more, even after a fresh reinstall?

It more sounds like some kind of DB corruption...
May be of index only ... Then on next start Valentina may be is able reindex
bad index...

If reindex happens then this is reflected in the Warning_log_xxx

-----------------
If problem happens on MAC, then you can and should check many things
a) crash log of your app
B) console app log to see any errors here.



-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]