griffo
|
| Posted: 05/28/2002, 4:19 AM |
|
I am trying out codecharge to see if it will fit my needs. I however cannot get past the first stage of getting my connectivity strings. I am on Windows XP.
After setting up MyOBDC I test connectivitry as ok, howver when I go to the Microsoft OLE DB Provider under the DATABASE option. I get the following error,
"Provider is no longer Available, Make sure the Provider is installed properly".
I have redownloaded codecharge and also gotten the latest 2.7 MDAC stuff from Microsoft. Help. I lost a whole weekend.
|
|
|
 |
Alex Alexapolsky
|
| Posted: 05/28/2002, 4:49 AM |
|
Do you get this error when you just load a list of Providers or after you
select MS OLE DB provider for ODBC drivers ?
I also suggest you to select "DSN" connection type right in
Site/Properties/Database tab.
|
|
|
|
griffo
|
| Posted: 05/28/2002, 4:54 AM |
|
Thanks Alex it is after I select.
MS OLE DB provider for ODBC drivers. I also tried ASP with IIS and JET 4.0 based on a tutorial I have and got same response. Is this a CODECHARGE XP or MyODBC problem? The fact that it happens also with ASP indicates it most likely is XP? Help.
|
|
|
|
CodeCharge
|
| Posted: 05/28/2002, 1:08 PM |
|
Hello,
This looks like an issue with drivers on your computer.
I recommend checking:
http://groups.google.com/groups?q=Provider+%22no+longer...led+properly%22
Also, do you have .NET framework installed?
If so, here is possible solution:
============================================
http://p2p.wrox.com/archive/aspx_beginners/2001-09/6.asp
============================================
My resolution was to uninstall IIS 5.0 and visual studio.net, then run a
clean install of win 2000 pro(didn't delete the partition, but I ended up
OK). Re-installed IIS 5.0, windows components(includes MDAC 2.7), and
visual studio.NET and was able to select my jet 4.0 provider and run the
test you had suggested. All is working! Thanks alot.
============================================
Konrad
|
|
|
|
griffo
|
| Posted: 05/28/2002, 2:47 PM |
|
I tried the .NET soulution. Actually I did not install IIS until a whol eday after having this problem. As a result I think it is something else. I even used the Microsoft MDAC COMPONENT checher. No dice.
I will try google though.
|
|
|
|
|
