Re: ODBC Read-Only Database Privilege
esimbo@my-deja.com wrote: > > With regards this problem you are experiencing, are you sayingh that > the Login Box does not appear when you are trying to run external > queries or vice-versa. That's correct. I get the login box if I run MS Query directly, but I don't if I start the query from Excel, which calls MS Query. When in Excel, a message box displays saying "Connecting to data source..." with a little animation. No matter how I move windows around, there is no prompt box. If, in the case of running MS Query directly I look at the prompt box, or in the case of Excel I pretend the prompt box is there, and then type my user name, TAB, my password, ENTER, I then get a successful login in both cases. > If it is the former, you can enable the Login Box by select the DSN in > the ODBC administrator and unchecking the No-login Box option. The behavior I describe is when the login window is endabled. When the login "window" is disabled, what it actually does is diable the whole login *process*, which the server side ODBC doesn't like because it's configured to require login. irwin_goldstein@my-deja.com wrote: > > I have seen quite a bit of > strangeness with OpenLink (and some other ODBC drivers as well) with > Office 2000 applications. For the most part these problems were solved > by downloading and installing the latest MDAC from Microsoft's web site. Probably very good advice. > It sounds like a client > side issue. Have you tried contacting OpenLink tech support about > this? I've found them pretty helpful in the past. They asked for a number of logs, etc., but in the end came to basically the same conclusion and didn't pursue it any further. I would think they would want to investigate that kind of thing, if only to give their helpdesk people a heads-up. However, they did take a look for an just an eval user, so I was happy about that. Guess it's time to look for a solution via the Office 2000 route. My Sympathy-O-Meter just moved a couple of ticks toward the DOJ side. :-) Thanks for the help, Walt. -- Walt Hultgren Manager, Information Technology Yerkes Research Center of Emory University Mailto:walt@rmy.emory.edu -- 404-727-0648
Hi Walt One thing that you might want to be aware of is that in the case of Excel, you must use File DSNs. In that case, you can edit the file directly by locating it in c:\\program files\\common files\\odbc\\data sources What option is there set for nologinbox. The other option would be as some gentleman mentioned of teh mdac option. HTH In article <39105A37.AE0FC846@rmy.emory.edu>, Walt Hultgren <walt@rmy.emory.edu> wrote: > esimbo@my-deja.com wrote: > > > > With regards this problem you are experiencing, are you sayingh that > > the Login Box does not appear when you are trying to run external > > queries or vice-versa. > > That's correct. I get the login box if I run MS Query directly, but I > don't if I start the query from Excel, which calls MS Query. When in > Excel, a message box displays saying "Connecting to data source..." with > a little animation. No matter how I move windows around, there is no > prompt box. > > If, in the case of running MS Query directly I look at the prompt box, > or in the case of Excel I pretend the prompt box is there, and then type > my user name, TAB, my password, ENTER, I then get a successful login in > both cases. > > > If it is the former, you can enable the Login Box by select the DSN in > > the ODBC administrator and unchecking the No-login Box option. > > The behavior I describe is when the login window is endabled. When the > login "window" is disabled, what it actually does is diable the whole > login *process*, which the server side ODBC doesn't like because it's > configured to require login. > > irwin_goldstein@my-deja.com wrote: > > > > I have seen quite a bit of > > strangeness with OpenLink (and some other ODBC drivers as well) with > > Office 2000 applications. For the most part these problems were solved > > by downloading and installing the latest MDAC from Microsoft's web site. > > Probably very good advice. > > > It sounds like a client > > side issue. Have you tried contacting OpenLink tech support about > > this? I've found them pretty helpful in the past. > > They asked for a number of logs, etc., but in the end came to basically > the same conclusion and didn't pursue it any further. I would think > they would want to investigate that kind of thing, if only to give their > helpdesk people a heads-up. However, they did take a look for an just > an eval user, so I was happy about that. > > Guess it's time to look for a solution via the Office 2000 route. My > Sympathy-O-Meter just moved a couple of ticks toward the DOJ side. :-) > > Thanks for the help, > > Walt. > > -- > Walt Hultgren > Manager, Information Technology > Yerkes Research Center of Emory University > Mailto:walt@rmy.emory.edu -- 404-727-0648 > Sent via Deja.com http://www.deja.com/ Before you buy.