When uploading a replacement database for one that is already on a server a dialog always comes up about a mismatched ID.
In this case I replaced a base named “prcdrs”
Everything seems to work without issue and the new database operates as intended. Seemingly it’s a false alarm and nothing is wrong.
admin
September 12, 2022, 9:51pm
2
Could you be more specific about what you are doing? Normally you would just do a new generation.
If you are transferring a database from one server to another, there is a report in the bug tracker about that.
I suppose the transfer would fit this situation. I do most programming on a copy running on my in-house server. When I have enough ready and running well, I unshare a copy then upload to the working server.
As I noted, nothing seems to malfunction. It’s a false alarm as far as I can tell.
admin
September 12, 2022, 11:36pm
4
Ha! Not only is this already in the bug list, but you also reported it previously a couple of months ago.
In order to make sure things are just right before loading changed procedures to a web server’s database, I typically make revisions in a copy running on my in-house server. When satisfied all is good, I replace the server copy.
Doing this last week I ran into a couple of issues worth noting.
I started by detaching a copy of the db from my server. Then I loaded it to the remote server via the Database Options and set for Sharing and Web Serving. It correctly asked if I wanted to replace the fi…
I thought it had come up some time ago but I couldn’t find it here .