Database with period in the name cannot be opened with a procedure

Panorama X
1

A newly shared database was downloaded and presents with a Lock in the Selected/Total Records box.

The Check Server Connection results with…

Not connected to server
The server Automation 21 is available but this database is not connected at this time. The database cannot be modified until it is re-connected to the server.

I press the Connect to Server and the reply is that it could not connect.

The Database Options Server tab shows Server: Automation 21 dimmed. There is a green check box in front of ‘Server connected’

2

I am successfully sharing other dbs for their first time without a problem. But this single database allows me to turn it into a shared db, but then I immediately get the locked icon. Then this…

Not usable
Not usable522×594 44.3 KB

3

Ok. Found the bug. I removed the period in the file name and all is good.

Argh.

4

Not a big deal, but it could be a nice touch to have file names evaluated before being shared.

5

I was not aware that there was a problem with periods in the file name. I’ve added this to the bug list, either it will be fixed, or it will be modified to prevent a database with a period in the name from being uploaded. My preference would be for the former if it is at all reasonable.

6

This turned out to be a general problem with periods in a filename, whether shared or not. For example, this code would not work:

opendatabase "my.mailing.list"

You could get it to work by using

opendatabase "my.mailing.list.pandb"

but that should not be necessary. I am amazed that no one has previously reported this in almost ten years.

The fix was super simple, and will be in the next release.