Every time I update either a procedure or a form or add a field to a shared database, I seem to break the database.
When the newly updated database is downloaded to a workstation, I either get the dreaded
"Runtime Call( failed" error or I get one of the following that appear on the server itself (yes, the server – not the client):
"Field or variable <some name> does not exist"
"Window not found"
I have several questions about this, in order of severity at this time:
- How do I revert to the previous generation/version of the database? (This is needed so my client’s work/business is not disrupted)
- How do I debug/troubleshoot these kinds of issues?
- What’s a “foolproof” workflow that allows me to update databases without ending up with these issues?
Note: before I uploaded the database, it was working as expected on my local machine.
Again, I appreciate all your assistance.