Use SQL Server ODBC, not Native Client.

I have setup 2 DSNs using ODBC32.

Bad Database Spec is a very bad error.  I've never seen it before.

Run Database Setup, and see what Verify says.

Has 3 errors in tables that I can't find in the Sage Object Model.

Your database doesn't match your programs.

Might be a red herring as I get the same errors in production.

Hi Rob, I hate to say anything different to Jay Converse Acumen but with version 6.0 I've always used SQL Native Client v9 (SQL 2005) which is installed with Sage Accpac ERP 6.0A workstation setup.  Jay probably knows something I don't but I could suggest you try it if you're still stuck.  Please see section 3-11 onwards of Sage ERP Accpac 6.0A - Installation and System Administrator's Guide (thanks Acute Data) for the instructions from Sage on how to set these ODBC connections up if you're having trouble.  You only need a single ODBC connection for all databases in Sage 300, and use the Server option not Data Source.  For clients like fund managers and construction that have 20, 30 or 50 databases, doing individual ODBC connections for each one would be a nightmare.  Providing you have the correct ODBC driver for your version of Sage 300, if you launch Database Setup as ADMIN, double-click on a database and click OK, it will generate and configure the ODBC connection for you, even in version 6.0A.  You shouldn't need to touch or manage the ODBC connection, providing you launch Database Setup with elevated rights.

Sounds like the Verify tool is failing because its encountering a setup its not expecting, but everything is working because it just happens to be a valid alternate configuration, just a theory...

The issue isn't that Sage can't connect to the database. The issue is that I can add anything related to thing in the OE module, orders, shipments, etc. If an order or shipment already exists, I can modify it.

Check you're running identical collation in Dev vs Production?

They are identical.

Can you clarify this one a little better in detail?

I open Order Entry, put in a customer, then do a lookup for an inventory item, put in the quantity and click Post. At this point I get the invalid database specification message. I can go through the same basic steps for a purchase order and it successfully posts. 

Hi Rob, If all your config is identical to production, and it works in production, then as you would be thinking, it should work in Dev too.  Using a different connection method/ODBC driver than recommended can cause problems like this so I do recommend working through the Admin guide I posted earlier.  The connection from Sage 300 to the Databases isn't it just works or it doesn't - you can make a connection and some things work and others don't based on the interpretation of driver - I have seen this before.  If you run the RVSPY logger from the RUNTIME folder it might give you the underlying error but it likely won't make sense as I suspect it will be a driver issue.  I thought about a table permissions issue too, but that would be very odd.  Overall all I can suggest is engaging a Sage Business Partner from here.

I'm wondering if Ops Inquiry is causing your issue.

If you're comfortable, edit the CSAPP table and remove the UQ record to test. 

Nope.

What am I looking for in the output window?