I have a database that uses a prompt in a navigator to collect information from a user before creating a form. The user's response is set in an ENVIRONMENT field. Certain information is then poplulated into the form when it opens for the user based on the prompt response. The default is the most commonly picked response (Response A). The user enters all of their data and then submits the form (or ticket) for approval.
In all my testing on the test server, it worked 100% of the time. For all users, when the form is created, it opens and populates fields appropriately. When the form was opened by a second user to do the approval, it worked 100% of the time, as well.
When I moved this to our production server, one approver opened the already created form (with the Response B settings - less common response) to approve the requested action in the form. When he opened the ticket, it reverted to the Response A form (or default response).
After looking into it, the only difference I see between his setup and the rest of the approvers, is that he has moved his notes.ini file to his N: (network) drive. The rest of us have the notes.ini file on our C: drive.
I verified that the environment field set was not defined in his ini file, but for those of us that opened a ticket to approve, it has been added to our ini files on our c: drives.
Is there a server or database setting that would allow the test database to check his network drive for the ini file, and the production database to not look for the ini file on the network drive?