I was going to start a topic about “does Pan X execute .Initialize on database startup like Pan 6 does” but I think this has morphed into another question. When I start up my “first” database, its .Initialize does a whole bunch of housework, defining variables and opening other files. Over to Pan X, nothing happens when I open the database. So I opened .Initialize to run it and see what happens. RIght off the bat it erred because the first file it tried to open hadn’t been moved over yet. So I moved it over, converted it and saved it. Ran .Initialize again and my database immediately disappears (crashed). Now when I try to open that database again it immediately crashes, which apparently answers my question: it DOES run .Initialize as usual. But I have a database that won’t open due to some conflict in the procedure. In Pan 6 I could use the Open Database wizard to prevent .Initialize from running, but I don’t see anything like that in Pan X. Is there something I can do about this?
And to complete my original question, does Pan X honor all of the “automatic” procedures like …ActivateForm, .Initialize and so forth as in earlier Pans?