thx nicole before i contact support can you tell me if you used views in your test? im wondering right now if the views are causing the issue. im going to see if there is a way from within netsuite to run queries using views instead of records like i've been doing. that way i can take the blame off ssms, odbc etc.

thx nicole, what about reposting to a TOTALLY DIFFERENT FORUM like sql central? if thats ok what do i do here first so i am not banned from this site? i dont really want to close this post. and i think it would be weird without specific permission to post a link to another forum in a post imade in this forum. regarding…

thx nicole, you are correct it is the same query but a totally different question. it runs no problem on the ui (where catalog "records" are targeted) with any where clause and no problem in this environment (where views are targeted) with a where clause that targets only one customer (can be a different one) row in each…

thx Nicole. i see it in ssms. the plumbing goes from a linked server thru a netsuite odbc/gateway product from CData to netsuite. the linked server shows only netsuite views. the target is a sandbox on one of our netsuite implementations.

thx nicole i will read it. we get a little nervous any time we see the word Connect in a netsuite related product. we never got a straight answer on where the simpler Connect product gets installed for getting netsuite erp data to our sql servers. our oracle account manager said it would be installed on both our netsuite…

thank you nicole. we opened a ticket with oracle and they explained that when 0 records are returned in that java "environment" they provided for us, that weird error occurs. who knew? we are good for now. we are new at this and we rely on that java pop up box for running suite ql queries. we dont know what db visualizer…

sure this is the product. https://suiteanswers.custhelp.com/app/answers/detail/a_id/107521/kw/107521 it may be a push product, it may not. That's the question so i dont know why you asked for details about the "push" product.. i've escalated the question at oracle. So far one gentlemen thinks its a pull. And the other a…

its not your fault, i'm not asking it right. yes richard is odbc connect a PUSH product? that's all we want to know. should i explain the difference between PUSH and PULL?

thank you Richard. So i think you are implying that the "connect" odbc driver is strictly a "push from netsuite" product? The answer to that questionis whta we are most interested in here. For consistency purposes, at this time i am averse to api's and web service like solutions. We are accustomed to and wanted to stay…