|Think about Loose Coupling|
Re: Win32::ODBC doesn't connect on browserby andreychek (Parson)
|on Jun 30, 2001 at 06:06 UTC||Need Help??|
Hmm... by any chance, do you have an error message you could paste into here? That might be helpful.
Also, it looks like you are running on Windows. Do you know what web server you are running.. such as IIS or Apache?
Lastly, do any other scripts on this server work when run by a browser, or is this the only one which seems to break? Thanks,
Update: Okay, after reading that FAQ you refered to, I do understand the question they answered, assuming it is the same problem you are having. They say:
When you create a DSN it is created under a particular account, which is not accessable from other accounts. If you are logged in as Administrator and you create a DSN called "Foo Database" then only processes running under the Administrator account can access "Foo Database".
They claim the only two ways to fix this problem are to create the DSN as the user the web server runs as, or create a system DSN. Okay, so what does this mean for you?
It sounds like creating a System DSN will be your best bet. The problem they are describing basically is saying that not every user has access to the DSN set up for your database. The DSN is basically a "pointer" that applications can use to find your database. A system DSN is one which is available to all users of your system. Do you have administrative rights to this web server? If so, make sure you have a System DSN set up for this database. You can find out by clicking Start->Settings->Control Panel->ODBC on your server.
If you don't have administrative rights, talk to you administrator, and have him verify that he does indeed have a system DSN set up for you. If he doesn't, tell him to add one :-)