Panorama X 10.2.0 b40 Build 4513 Release Notes

[admin]

As promised, the “official” b40 release is now available, replacing the experimental version released last week. Most users can simply let Panorama automatically update. The only reason you would need to manually install this version would be if you are running macOS Sequoia and you did not install last weeks experimental b40 version. Hopefully none of you fall into this category, but if you do need to manually install, the direct download link is:

https://www.provue.com/downloads/sparkle/PanoramaX/4513/PanoramaX.zip

Or, you can simply go to http://www.provue.com and download the trial version, which is the same version.

In addition to fixing the problem with Sequoia, this release also includes updated documentation, and includes the changes below.

• Panorama no longer allows the user to click to change window order while a procedure is running.
• When opening a shared database Panorama prevents window switching or running other procedures until synchronization is finished.
• Implemented the webshare statement (brought over from Panorama 6.0).
• New nanzero( and nanerror( functions provide additional flexibility in dealing with invalid floating point values.
• The View and Action menus now work correctly with form and procedure names that contain the } character.
• Double chevron notation now works in the formulavalue function and statement, and formulacalc. (This means that it now works correctly in the Formula Workshop, and dialogs like Morph > Formula Fill.)
• The selectrelated and selectrecordsrelatedto statements now work even if the specified relation options aren’t all in upper case.
• The BinaryDataBuild( function now works correctly with double chevron notation.
• Fixed pattern( function for scientific/engineering notation with small numbers and negative numbers.
• Creating a new database with an imported text file with field names now strips off any blank lines from the beginning and end of imported data.
• The PrintToPDF statement COPIES option now works correctly if default printer specified.
• Updated Zip Code information with July 2024 data from US post office.
• Panorama now now automatically opens the Site License window if you are not logged in.
• Oops. Misspelled “dictionary” in seven error messages!! Now fixed.
• Documentation of info(“guid”) function now mentions UUID as well as GUID.
• Documentation corrections from David Thompson, Peter Newble, James Cook, Robert Ameeti, David Scott

[JamesCook]

On two separate computers, both running Sonoma, Panorama X Server kept launching as b39. I tried on a third computer and server stays at b39.

Manually deleting Panorama X Server didn’t work either. When I tried starting Server then, I got a message: Warning: Download of PanoramaX Server.app may be corrupted!

So for now I’m running Panorama b40 and Panorama X Server b39.

[admin]

I was able to duplicate this, so I’ll have to investigate to see what is going on.

[Mac]

Anybody else experiencing this since updating when selecting a topic in the Help window?

[pcnewble]

Yes, same here.

[KJM]

macOS Sequoia 15.0.1 seems to have solved the wide-spread Firewall problem that caused many apps to lose their internet connectability.

Jim, has the update cleared that API issue, too, that you worked around with b40?

[JamesCook]

On a server that does a restart each night, we can’t stop the notice for the b40 update from appearing when Panorama launches. It sometimes interferes with automated tasks.

Choosing Skip doesn’t take.

Sometimes it launches with the wrong menus set

OS is Sonoma

[JamesCook]

@admin

I was able to duplicate this, so I’ll have to investigate to see what is going on.

FWIW, this is the same as the issue we had on b39

Panorama X 10.2.0 b39 Build 4486 Release Notes

On three computers, the update installed properly. But stopping then restarting on two, the server is not loading the updated version. Even a Quit is not causing it to install the new server version. On the third machine, the server had not been set up and running so no stop was necessary, but it also failed to load the new server version when the server was started. I couldn’t find past references to this part of the update process, but memory is that this is the prescribed way to update the …