Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
MSAccess 255 Column Limit
MSAccess has a limit of 255 columns on any queries that are run locally with the MSJet engine, and the 255 limit also impacts the list of fields that MSAccess pulls from the database and presents to you in the drop-down menu of field names (i.e., Access only shows you the first 255 fields).
In the old Oracle9i driver, I could code a "pass-thru" SQL query that would send the SQL string directly to the Oracle server and run it at the server (instead of running it locally in MSJet engine). I could include any fieldname in this pass-thru query string and Oracle would return the data to me, thereby working-around the 255 field limit in Access (plus the server-side queries are much faster since Oracle does all the lifting server-side and just returns the results via XML stream to the client)