You may need to comment out the datapipe line for that form in the associated ini file (such as POrpt.ini in the PO program folder, if the problem is a PO form).  I had the same situation recently and that solved it.

But now that I have reread your post - I will give that a try.

Thanks

At some point, Sage told us we don't have to edit rpt.ini files anymore, but in some cases that's not true.  The default PO form, for example, uses a .dll so the default .ini file says it's a datapipe. In order to bypass that instruction and go straight to ODBC, try commenting that line out.  I think it has something to do with when the SQL database ID is not identical to the Sage database ID that this instruction gets read, and we want to skip it.

At some point, Sage told us we don't have to edit rpt.ini files anymore, but in some cases that's not true.  The default PO form, for example, uses a .dll so the default .ini file says it's a datapipe. In order to bypass that instruction and go straight to ODBC, try commenting that line out.  I think it has something to do with when the SQL database ID is not identical to the Sage database ID that this instruction gets read, and we want to skip it.

Thanks - I am going to give it a try first thing in the morning.  Appreciate the advice.

Howard

Update:  another client (recently upgraded) had this issue today with 2 OE Invoice forms.  One prompted for database login, and the other came up blank.  Commenting out the datapipe line for OEINV01 in oerpt.ini solved both issues.

Thanks - I just gave this a try and still being prompted for SQL credentials