Can you post your code? Did you make sure to check that the database has the same name on the new server (if you’re using servername:filename)
That the signer or user of the agent has permission to access the database on the new server?
I had this happen a lot in R5 - the user’s client doesn’t know how to connect to the server, or the database is being referenced by a replicaID and the user doesn’t have the replica on their workspace.
Sometimes just dropping the new server’s address book on the user’s workspace, or dropping the link to the lookup database resolves the problem.
I’ve seen the error both when the user’s client can’t see the server and when they don’t have permission to access the database.
In that case, you may need to open, edit and save the view selected in the “use view-dialog”, since it will have pointers to the original server (SERVER HINT).
Then if that doesn’t work, then on the user’s desktop, do File>>Database>>Open and type in the NEW Server name if it doesn’t appear in the server list, and navigate to the database on the new server. Once it’s open, close it and try your button again.
Try deleting your original field on the form, save the form, and then recreate the field, being sure to point the lookup to the right server and view.
As a test, add a temporary button that will open a picklist and drop the selected items into the field.
Sometimes the workspace caches old values, and I avoid using the “use view dialog” for this reason… too hard to step through and do a global change when the server changes.
I usually add a shared: LOOKUP_SERVER (and filename) field to the top of every form so I only have to change it in one place should the server or filename (or replica ID) change.
Thank You - it works.One problem was that I had the same db-name on the
database and the template - mydb.nsf and mydb.ntf
and when I should select the database in the “look-up-dialog” I got two similair names: “mydb”. So how do you name your templates - I suppose not the same as the db?