Launch DB sets

[Elon Close]

Panorama has the nice feature of creating a file that launches sets  
of DBs.

I have an address program that uses this feature and has been running  
for about 6-7 years, right thru version 4.x. It has no problems  
launching and running.

With version 5.5 there is a launching problem which can be summarized  
as:
The first DB, call it DB1, that is launched will open and an error  
message is issued.
File DB2 not found. Clicking again on the DBset file will then launch  
DB2. This occurs when DBset launches Panorama, i.e. Panorama is not  
open and running. If Panorama is open, no message and DB1 and DB2 are  
launched.

The “problem” can be summarized as:
DB1 cannot contain a .Initialize procedure that has ANY statements.  
Comments are ok. DB2 can contain a .Initialize procedure, Panorama is  
by then open. If Panorama has been opened before DBset is used, there  
is no problem.

I have verified this by creating 2 very simple DBs, DB1 & DB2, that  
have no data, each has only an empty Data form with 3 empty fields.  
Create a set DBset to open these DBs and all is ok. Put into DB1  
a .Initialize procedure with no statements, all ok. Put in one simple  
statement, Local test, and the message appears and DB2 is not  
launched. Other simple statements like window cause the same problem.

I tend to use.Initialize procedures to define variables, set up  
information, run opening procedures. In this particular case  open a  
simple window with a button that takes me to where I want to do work.  
It is easy, in this case, to put  initialization information in the  
procedure that this button uses.

For me this has only caused a fair amount of Panorama time to find  
the “problem” so that I could enter a new address. And on the  
positive side a Big Thanks to Jim and the Panorama Staff for the  
ability to copy paste forms, to copy paste procedures, and the  
ability for a Panorama DB to read and use the data of another  
Panorama DB without having to do a messy export. After finding the  
“problem”, the original DB launched ok after the removal of  
the .Initialize procedure from DB1.

Best Regards
Elon Close