I have created a single combobox field with a @DbColumn SQL ODBC lookup. When the form is launched in the client the lookup returns the data from the SQL server. When the form is launched on the web the page will not load.
HTTP session authentication is enabled on the server.
Forms without the SQL ODBC call load properly on the web.
Could this be a server config issue?
Thanks for the help.
Subject: SQL ODBC not working in Web
Hi Greg,
I was going to ask if you’d configured an ODBC data source on the Domino server itself, but then I saw that you’re using @DbColumn to retrieve the information. According to the “Usage” section of Designer help for @DbColumn (ODBC data source):
“This function only works in Web applications if the remote server hosting the table from which data is being retrieved exists on the same machine as the Domino server, which is rarely the case.”
Probably not the answer you wanted to hear…
-Stephanie
Subject: RE: SQL ODBC not working in Web
That’s very strange. The exact same code is on our production R5 server and everything works fine on the web. Has @DbColumn been changed in R6?
FYI: The R6 DB is on the server and the @DBColumn works in the client.
Thanks Stephanie
Subject: RE: SQL ODBC not working in Web
Hm, interesting. To be honest, I don’t know whether or not it’s been changed, I just saw that note in the help and thought it might apply. But then you got me wondering, so I looked it up on the R5 help. Guess what? That paragraph isn’t there at all. (A quick check in the KBase and in this forum didn’t seem to turn up anything definitive about it, but maybe someone else around here can jump in with more details…?)
Dumb question - is your R5 server installed on the same machine as your SQL server? Out of curiosity, what’s the actual error that gets reported to the log when you open the form on the web?
Just for kicks, let’s assume for a moment that it does work in 6.x… I’d tell you to check and make sure there’s an ODBC DSN configured on your Domino web server. It needs the same name as whatever you’re supplying in your @DbColumn argument for the data source parameter. (If your R5 server works with the exact same code, then you can look at the R5 server’s ODBC data sources and copy the settings for the one it’s using for this connection.)
(FYI, the fact that everything works from the Notes client just means that your client machine already has such a data source configured. But when you’re dealing with web applications and scheduled agents, then everything happens from the server, so it’s the server that needs the data source info, not the client.)
Bottom line, even if the @DbColumn has been changed and will no longer work (and what a pain that would be!), rest assured that there are other things you can do to achieve the same functionality. Some are easier than others, of course…
-Stephanie