and the second of two databases listed as auxiliary databases does not open.
Start PanX, 10.2.0.b9 (3435) by click the dock icon for a shared database (in my case, “Navigator”
Use a Navigator procedure to open a second (non-shared) database named “BP”
BP has two auxiliary shared databases, “SD Matters” and “Timekeepers”. Both have .Initialize procedures.
Result: SD Matters opens but Timekeepers does not. I repeated this several times.
To my surprise, I change the order of the Auxiliary databases, both databases opened normally (not secret) and their .Initialize procedures ran. The Auxiliary function seems to have stopped working as intended. [Added note: Sorry. I forgot to mark them as open with no windows after putting them back in place.]
I am in the process of downloading another copy of b9, but it’s moving dreadfully slow. (8 kb/sec-a bad dialup modem). I’m stopping that and will try again later.
If changing the order back causes the problem to occur again, please open the Instrumentation panel and choose the Launch with Shared Database option by clicking on the star, then we can see what is going on.
Am I correctly reading this added note as cancelling the previous sentence?
More good bad news, to channel John Lewis. One person uses BP in the firm. That person has now reported the failure of the second aux db to open, but only if BP is opened for the first time. If you close BP then reopen it, both aux dbs open secretly as they are supposed to do. The problem has disappeared from my computer since reinstalling b9, but I wonder if you want to run some diagnostics on her computer before we reinstall b9?
The same user has another (shared db) that opens the same two aux dbs. I cannot get the same failure to occur with that one.
I definitely want to know what is happening, so if the diagnostics can help, when I would like to turn on the correct thing. Can you give me directions on what to turn on?
I got your log. Are you sure you selected the Launch with Shared Database instrumentation? From the log, it appears that you selected the Shared Database Open & Close option.
In any case, the log doesn’t include the auxiliary database information. Let’s skip the star menu, you can set up the necessary instrumentation with this link, hopefully you can make the problem occur again.
Once you make a log, you can verify the settings because they are recorded at the top of the log. Here’s what your settings say, you can see that they are quite different from the link I send you above.
Even without this information, I think I see the area of the problem – it’s another secret database issue. Looks like it will occur if the aux database is secret, AND if it needs to be synchronized. I’m a bit puzzled you are not seeing an error alert pop up. If you can get it to happen again with this new coverage link that would be helpful I think.
I’d still like to see the additional log if possible, but based on the log you already sent I think I see that this problem could occur just in the combination of a non-shared main database with shared auxiliary databases that are opened without windows. Any other combination should work.
