[shanondink]

Hi everybody,

About an hour ago, I successfully downloaded and installed the new driver but when I get to the window to pick a Company and Role, our company name (which has a comma in it) is broken into different selections in the drop-down and the “Role” has like 3 blank selections. This is using Excel and Access.

Also, anybody got it to work in vb.net? I have not had time to dig very far right now, but it breaks my vb.net commandline app.

Last, is it possible to pre-define a Company and Role? In Excell/Access? In vb.net?

Thanks in advance,

Shanon
This is a cached copy. Click here to see the original post.

[mhuffman]

Hi Shanon,

Please file an case with support regarding the “company name with a comma” issue and we will investigate.

As a workaround, you can define Company/Role in your data source (DSN) and create a unique DSN entry per company/role. This should also fix your vb.net app.

In help, search for Setting Up Enterprise Reporting Views and open the PDF. Page 6 describes how to edit your DSNs to specify company and role.

[longlam]

RE: New ODBC Driver Problems

Hey Malin,

I just noticed that the path to the registry files maybe incorrect. You have:

My Computer > HKEY_LOCAL_MACHINE > ODBC > ODBC.ini > NetSuite.com

But my path is:

My Computer > HKEY_LOCAL_MACHINE > Software > ODBC > ODBC.ini > NetSuite.com.

Just in case anyone else is the same.

[shanondink]

RE: New ODBC Driver Problems

Thanks Malin,

I have a case # 648009 open, but we are free support so I don’t know when/if it will be looked at

The work around didn’t work for me but I am assuming it is still the comma causing problems.

Also, like longlam, my path has “Software” in it as well.

Sorry I didn’t try the beta but I am swamped around here these days.

Thanks again,

Shanon

[mhuffman]

Thanks Long… on my computer it is as specified in the guide.

What version of Windows are you running?

[mhuffman]

Shanon, one other thing.. I notice your company name has both comma and period – when you edited the DSN registry to add company/role, did you swap out the period (.) in your company name with an underscore (_) ?

[longlam]

RE: New ODBC Driver Problems

Originally posted by mhuffman

Thanks Long… on my computer it is as specified in the guide.

What version of Windows are you running?

I’m running Windows 2003 Server. BTW, I haven’t had any issues so far using the new beta and now production. I’ll have to check in to see if some of the limitations revolving around multi-joins and subqueires are now resolved but haven’t had much time. Keep up the good work.

[galaxy]

RE: New ODBC Driver Problems

Malin,

I’m running XP Pro and the path is the same as Long sees:

..Local_Machine>Software>ODBC.ini>Netsuite.com

Any sample code available for Excel VBA using ADO?

Galaxy

[mhuffman]

Ok, we’re going to update the help to reference both paths to the DSN in the registry since either appears valid, depending on your system.

[smudgiebottom]

Hi,

I’ve got the new version installed and through our firewall now (that port number change to 1707 is really annoying!), but large queries that used to run on the old ODBC driver now get “unexpectedly disconnected” whilst refreshing. Small queries work fine (as expected), but anything over 200,000 lines or so (using Excel 2007) seems to disconnect.

Does that make sense? Is there a limitation/timeout that can be adjusted?

I understand the security reasons for it, but I am just trying to avoid rolling it out to other users if it is going to hamper them.

Any ideas Netsuite?

Cheers,

Matthew

[mhuffman]

200,000 results shouldn’t be a problem… could you try it again tonight or tomorrow and let us know if you still get disconnected, and if it’s at the same point? The only thing I can immediately think of is that maybe the ODBC server required a restart in the middle of your results and you got bumped. This should not happen consistently, though… if so, please file a case so our engineering team can investigate further.

[smudgiebottom]

Thanks Malin,

I’ll try again later and let you know if any change.

Cheers,

Matt

[Bakers’ Best]

Originally posted by mhuffman

Shanon, one other thing.. I notice your company name has both comma and period – when you edited the DSN registry to add company/role, did you swap out the period (.) in your company name with an underscore (_) ?

I am also having the same issue with the company name. The period has been swapped with an underscore, the comma is not present, and the name shows up on two lines. There is no choice available in the role dropdown. We use it with Microsoft Access. I have not been able to connect.

Tim

[longlam]

RE: New ODBC Driver Problems

Bad news Malin, when installing the new driver I didn’t release that you were updating only the system DSN not the client DSN. I soon realized this and have finally gotten a chance to try the new driver to no avail.

Before delving into the issues I think you should make more clear in the documentation what we should put for the company name and role value in the registry when using jdbc/odbc. In the end, I was most confused with the role value as I’m unsure if I should have the string “Administrator” of the internal id or the role internal id which is 3. In terms of being consistent, I am used to using internal ids for any information I pass to Netsuite especially through the use of web services and I would hope that you will make the registry values consistent as well. I am further confused because when using Access of Crystal Reports and I am prompted for information, I am shown that the titles for the company and role information include “label” as suffix which leads me to believe that the information shown is just the string whereas the internal ids are passed back to Netsuite? Please clarify this point for me. In programming, we do this all the time to show the user the information they need to make the decision but pass back integer values since that it is safer and less prone to mistakes.

I use the odbc connection in many ways. Two of the ways are basically the same, via Access and Crystal Reports. In my tests today at around 5PM PST both pieces of software hung and I had to forcefully exit. In other occasions I get the error that I should close my application and try again which I have done without any success. This testing was done with the registry values deleted so as not to interfere with the values that were passed via the prompt.

I also used the odbc driver in many parts of our java integration applications and the jdbc/obdc connection is also not working.

I’ve done some testing with this and here are the results:

No registry values

java.sql.SQLException: [SimbaLNA][unixODBC]NotEnoughConnInfoButDriverNoPrompt/1, which seems correct since I have not filled those values in.

Company Name=String, Role=String

Company Name=String, Role=Id

Company Name=Id, Role=Id

[SimbaLNA][unixODBC]DataSourceDidNotGiveProperResp/1

Looks like I am connecting correctly but the odbc system is not responding to my requests. I’m hoping this is a server issue on your end and you may need to just restart it. I have checked the old driver using the old port and the connection works as expected. Please give me a call at the number on our account if you’d like to discuss the issue further. I’m going to try again tomorrow morning hoping it is a server issue and if not I will call support.

[mhuffman]

We have updated the help to more precisely advise which values to use in your DSN for company and role. I agree this was confusing. It should have literally been the company/role names as they appear when you log into NetSuite (in the upper right corner of the application window.)

Please see my post below for an update… in response to feedback, we have managed to extend the operation of the old ODBC driver beyond Nov. 29. This will give us all a better chance to become more comfortable with, and iron out issues with, the new driver.

https://usergroup.netsuite.com/users…ad.php?p=48079

[Author]

Posts