I cannot access my Access databases that I post to my Windows 2000 

server.  ASP and COM routines run fine on my development machine (Windows 

2000 Professional)  reading and writing data perfectly.  But when I 

transfer my database it stops workings.

 

When I post Access 97 and Access 2000 database to the server I get two 

access problems.



1)	ASP 3.0 using ADO will read, but not update data.  No matter what 

parameter values I set in the connection object or the recordset object 

the Access 2000 database will only give me read only privileges



2)	My COM can not access the Access 2000 with ADO or the Access 97 

with DAO.  In both case I get an error message that the database is opened 

exclusively by another user.





I have triple checked my opening settings on Access and tried both mdb and 

mde file modes.



Someone please tell me what I am overlooking!



Thanks, 





Paul Bullock

I had something similar and after bashing by brains for a few days I 

finally found something that fixed it, though it makes no sense to me.



In access97, under tools->security->user and group permissions, I set all 

the tables and queries to UNchecked for all users but the admin.  The 

Admin has everything checked.  I have an iuser in there as a user, but I 

don't know whether this makes any difference.



hth



maybe you can clear up this mystery:

Using an oledb connection, I MUST put my sql statements in the asp page.  

With oledb, if I put the sql statement in the db and call it from the asp 

page, I get an error error:



Microsoft JET Database Engine (0x80040E14)

Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT',

or 'UPDATE'.



What's up with that?







> I cannot access my Access databases that I post to my Windows 2000 

> server.  ASP and COM routines run fine on my development machine 

(Windows 

> 2000 Professional)  reading and writing data perfectly.  But when I 

> transfer my database it stops workings.

>  

> When I post Access 97 and Access 2000 database to the server I get two 

> access problems.

> 

> 1)	ASP 3.0 using ADO will read, but not update data.  No matter what 

> parameter values I set in the connection object or the recordset object 

> the Access 2000 database will only give me read only privileges

> 

> 2)	My COM can not access the Access 2000 with ADO or the Access 97 

> with DAO.  In both case I get an error message that the database is 

opened 

> exclusively by another user.

> 

> 

> I have triple checked my opening settings on Access and tried both mdb 

and 

> mde file modes.

> 

> Someone please tell me what I am overlooking!

> 

> Thanks, 

> 

> 

> Paul Bullock

Does the file have write permissions on the server?  I had the same problem 

and my ISP took care of it by setting permissions correctly.



Mitch







At 07:23 PM 2/20/2001 +0000, you wrote:

>I cannot access my Access databases that I post to my Windows 2000

>server.  ASP and COM routines run fine on my development machine (Windows

>2000 Professional)  reading and writing data perfectly.  But when I

>transfer my database it stops workings.

>

>When I post Access 97 and Access 2000 database to the server I get two

>access problems.

>

>1)      ASP 3.0 using ADO will read, but not update data.  No matter what

>parameter values I set in the connection object or the recordset object

>the Access 2000 database will only give me read only privileges

>

>2)      My COM can not access the Access 2000 with ADO or the Access 97

>with DAO.  In both case I get an error message that the database is opened

>exclusively by another user.

>

>

>I have triple checked my opening settings on Access and tried both mdb and

>mde file modes.

>

>Someone please tell me what I am overlooking!

>

>Thanks,

>

>

>Paul Bullock

>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

PenPrints - Clamshell Boxes, Hand Bound Books,

and Fine Art



http://www.penprints.com

Re the oledb connection error (expected 'DELETE' etc.), I got the same in 

trying to open a query through ADO where there were spaces in the query 

name (e.g. "My Query Name"). Removing the spaces seemed to do the trick.



Might be worth checking for similar problems with the name of the ASP 

page, or the query name if you are using a query as the source of your SQL.



By the way, this was in means a thorough isolation of the problem - I 

simply found what made the error disappear for me. It may have resulted 

from flawed code on my part also!



Andrew.





> I had something similar and after bashing by brains for a few days I 

> finally found something that fixed it, though it makes no sense to me.

> 

> In access97, under tools->security->user and group permissions, I set 

all 

> the tables and queries to UNchecked for all users but the admin.  The 

> Admin has everything checked.  I have an iuser in there as a user, but I 

> don't know whether this makes any difference.

> 

> hth

> 

> maybe you can clear up this mystery:

> Using an oledb connection, I MUST put my sql statements in the asp 

page.  

> With oledb, if I put the sql statement in the db and call it from the 

asp 

> page, I get an error error:

> 

> Microsoft JET Database Engine (0x80040E14)

> Invalid SQL statement; 

expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT',

> or 'UPDATE'.

> 

> What's up with that?

> 

> 

> 

> > I cannot access my Access databases that I post to my Windows 2000 

> > server.  ASP and COM routines run fine on my development machine 

> (Windows 

> > 2000 Professional)  reading and writing data perfectly.  But when I 

> > transfer my database it stops workings.

> >  

> > When I post Access 97 and Access 2000 database to the server I get two 

> > access problems.

> > 

> > 1)	ASP 3.0 using ADO will read, but not update data.  No matter what 

> > parameter values I set in the connection object or the recordset 

object 

> > the Access 2000 database will only give me read only privileges

> > 

> > 2)	My COM can not access the Access 2000 with ADO or the Access 97 

> > with DAO.  In both case I get an error message that the database is 

> opened 

> > exclusively by another user.

> > 

> > 

> > I have triple checked my opening settings on Access and tried both mdb 

> and 

> > mde file modes.

> > 

> > Someone please tell me what I am overlooking!

> > 

> > Thanks, 

> > 

> > 

> > Paul Bullock