469,286 Members | 2,442 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,286 developers. It's quick & easy.

Server.CreateObject("ADODB.Connection")

ADODB.Recordset "The connection cannot be used to perform this operation." "Microsoft Access Driver"
ERROR 0X800A0E7D

OLE exception from "ADODB.Recordset": The connection cannot be used to perform this operation. It is either closed or invalid in this context. Win32::OLE(0.1707) error 0x800a0e7d in METHOD/PROPERTYGET "Open"
!stupid registrations!

!STUPID FORUMS!
STUPID MICROSOFT
!NOTHING WORKING!

!!! WHY IT WORKS LOCALY !!! WHY IT WORKS LOCALY !!!
!!! AND NOT WORKS UNDER APACH OR IIS !!!

the L: drive is mounted from other computer (if its mater)

STUPID PERL
$DSN = "PROVIDER=MSDASQL;DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=$DBFile; UID=Administrator; PWD=dns893;";
$Conn->Open($DSN);
$RS->Open($SQL,$Conn,1,1) or print "Open Exception!" .br .Win32::OLE->LastError .hr;

STUPID VB
'Create a connection object.
Set cnn = Server.CreateObject("ADODB.Connection")
'Open a connection using the OLE DB connection string.
cnn.ConnectionTimeout = 5
cnn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=L:\FM07.MDB"'Instantiate a Recordset object.
Set RecSetWaterPicks = Server.CreateObject("ADODB.Recordset")

!!!! ANY ONE PLEASE HELP !!!!
!!! STUPID OFFICE WANTS TO USE STUPID ACCESS !!!
!!! WHY PIOPLE LOVE USING STUPID APPLICATIONS !!!
Aug 7 '07 #1
7 9950
PLEASE HELP ME FAST
it works calling perl ... and not as cgi ...
PLEACE KNLAGE GUYS !!! HELP
Aug 7 '07 #2
ODBC driver does not support the requested properties.
Aug 7 '07 #3
numberwhun
3,503 Expert Mod 2GB
PLEASE HELP ME FAST
it works calling perl ... and not as cgi ...
PLEACE KNLAGE GUYS !!! HELP
First, please know that in the forum, there are no emergencies. Your emergencies do not apply to us. Everyone has the same priority......none.

Second, calm down, take a DEEEEP breath, and BREEEAAAAAATTTHHHHHHH!!!. Comments like "STUPID FORUM", "STUPID PERL", and others won't get you anywhere and just make you sound flustered and overwhelmed.

Now, we need some more information. For instance, more code if you can. We need to see what modules you are using and what you are trying to do. We cannot help you with the VB, but hopefully someone here knows the answer to your issue with Perl.

Also, what errors are you getting that are causing you to believe there is a problem? Can you copy and paste them here please?

Calm down and we can help. Getting yourself worked up into a tizzy and nearer to a stroke or seizure will not do anyone any good. A level head works best in the worst situations.

Regards,

Jeff
Aug 7 '07 #4
SORRY!, I'm realy sorry.
Ok
there i found that my mdb uses linked databacess from mounted hared hd
and that is not supported...
Microsoft JET Database Engine (0x80004005)
'L:\DNSVER50.MDB' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
I' getting that error from:
Set cnn = Server.CreateObject("ADODB.Connection")
cnn.ConnectionTimeout = 5
cnn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\DB.MDB"
Set rstCustomers = Server.CreateObject("ADODB.Recordset")
strSQL = "SELECT * FROM Customers WHERE CustNo < 100"
when I use linked drive directly as L:\DNSVER50.MDB it throws
file not found...
Is it me or any help or sujestion
....
Aug 7 '07 #5
L:\ = LINKKED HD From other network Computer
DB uses links to tables on this (MAPPED) drive.
then path not found but Access works OK no problem!
Adrian
Aug 7 '07 #6
Microsoft JET Database Engine (0x80004005)
The Microsoft Jet database engine cannot open the file '\\Server\ACCESS\DNSVER50.MDB'. It is already opened exclusively by another user, or you need permission to view its data.
Aug 7 '07 #7
numberwhun
3,503 Expert Mod 2GB
Microsoft JET Database Engine (0x80004005)
The Microsoft Jet database engine cannot open the file '\\Server\ACCESS\DNSVER50.MDB'. It is already opened exclusively by another user, or you need permission to view its data.
It sounds like you have gone from not being able to connect to not being able to access the resource because of either permissions or a locked file. I would say that is some progress, but not a Perl issue.

Regards,

Jeff
Aug 8 '07 #8

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

reply views Thread by Andrew Durstewitz | last post: by
reply views Thread by Jim Moon | last post: by
2 posts views Thread by Jim Moon | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.