I’m finding multiple problems with B40 on a M2 laptop running Ventura 13.7. I’m running a 30 min+ programmed series of inputting cvs files into multiple dbs then analyzing the set of dbs. The whole thing, with same inputs, runs fine with B39. My ‘master’ db [“WS Updater”] has a form [“Multi-Import”] via which I can check on/off which modules of input or analysis to run.
The first cvs imported leads to “PanX expectedly quits” at multiple steps (commenting out found problem lines, then rerunning to identify more problems), after successfully importing the cvs. Instrumentation showed quits occurring at code lines using formulafill date() to transfer a text date field into a date field. Using formulafill time() to transfer a text time field to a numeric time value field also unexpectedly quits. Sequence 1,1 in a previously empty numeric field brought up the Error Wizard:
A stop statement before the lines unexpectedly quitting, then using Morph dialog to manually do the same code worked fine in each case. A couple trys of importing other single files showed another resulting in false quits and one that actually did run ok. Haven’t had time to test all the individual modules yet.
Moreover because of the potential length of the overall set of procedures, I’d added years ago a very early alert statement so I could abort before everything checked ran. Initially with B40 that alert statement displayed two, identical offset but partially overlapping versions of its dialog.
Clicking the top level dialog resumed the subsequent program flow, but left the lower dialog displayed. More oddly triggering the alert statements procedure via the Action menu, or via a button (containing a call to it) displayed the double alert, but triggering it from its procedure window’s run button displayed just one. Running just that alert statement, in a new procedure, displayed the expected one dialog, implying that code prior to it contributed to the problem. The alert statement occurred early in the code. After a series of Local, Permanent, Global and Define statements and one assignment statement there were a few lines intended to ensure sure the ‘master’ db’s form window was open, but its datasheet was not. That code had worked since early versions of PanX, but now seemed imprecise to me:
opensheet
openform "Multi-Import"
opensheet
closewindow
openform "Multi-Import"
alert "No,Yes,Cancel","Really run DoIt(=Cancel)?"
So I rewrote it to:
If info("windows") notcontains "Multi-Import"
openform "Multi-Import"
endif
if arraycontains(info("windows"),"WS Updater",cr())
window "WS Updater"
closewindow
endif
window "WS Updater:Multi-Import"
alert "No,Yes,Cancel","Really run DoIt(=Cancel)?"
With the new code the Alert statement under B40 displays just a single working dialog regardless of the trigger. So I’ve resolved my double dialog problem without understanding why it occurred with the old code under B40 and never had with B39. [The odd parameters for the alert buttons were to prevent my bad habit of prematurely hitting Return and thus having the long procedure run. With this, hitting ESC runs the procedure, Return aborts it. Better for odd me!]
For me for now running my weekly long procedure set under B39 seems my best solution. Even if the unexpectedly quits could be fixed at my end, just identifying where all the fixes would be needed seems tedious — I’ve only tested a small fraction of the total code so far under B40. And the ones I have identified are in a database full of HIPAA protected data which I can’t send ProVue as is. I hope the above partial info helps find a solution from ProVue’s end. Ventura is getting old. I’m willing to update to Sonoma whenever I find the time, but prefer to wait on Sequoia until its problems are solved.