Puzling problem with on-line Access data

[Douglas J. Steele]

I'm not sure that checking TData.Supports(adUpdate) actually means that your
specific connection is updatable: I think it just means that the OleDb
provider you're using supports updates.

Usually ASP runs under the security context of IUSR_<name of computer>. Make
sure that that id has the correct permissions on the folder where the MDB
file exists. You require a minimum of Read, Write and eXecute, and Delete is
usually recommended as well. (Giving "Change" access is usual). This is
because you need to be able to create the logging file (.LDB) in that folder
in order to be able to update the database.

 

[Neil Gould]

Hi,

I am trying to update an on-line database using VBSCRIPT / ASP and have
run into a very curious problem. Some preface details:

* I am able to read the data without problems, so the database connection
is valid and functional.

* I created a test applet that supposedly returned the supported Recordset
methods.

Using the exact connection code that reports that this method is supported
in the test applet:

IF TData.Supports(adUpdate) THEN
Response.Write("adUpdate = Yes")
ELSE
Response.Write("adUpdate = No")
END IF

Reports:
adUpdate = Yes


I run the method in the actual app:

IF TData.Supports(adUpdate) THEN
TData.adUpdate PWFN, PWVal
END IF

with the resulting error message:
-----
Microsoft VBScript runtime error '800a01b6'

Object doesn't support this property or method: 'PData.adUpdate'

/test/application.asp, line 291
-----

It appears to me that the server accepts the code as valid then bombs out
when it actually executes it. Any idea what might be happening?

Thx

Neil

 

[Paul Shapiro]

If your site is externally hosted, and offers Access mdb support, the hoster
should be familiar with the necessary security settings. Send them an email
and ask them to verify the website account accessing the db has the
appropriate permissions.

 

[Neil Gould]

Hi Douglas,

Thanks for your quick response. To address some of what you've raised; our
database resides on a host that I have no direct access to, so I would
need some way to check security permissions remotely, if that is the
issue. Any ideas?

I was able to write to the database in the past using another method that
now also fails with a "...needs updatable query" message, which is why I
was trying a different approach. I have not noticed the creation of an
..LDB file in the folder at any point in the last few years.

Neil

 

[Neil Gould]

Hi Paul,

Thanks for your response, though I've probably been unclear about the nature
of my problem. I had set the permissions via the ISP host's interface years
ago, and double-checked that they hadn't changed after Douglas' last
message. The directory with the mdb files has write privileges, and in the
past, other ASP code was able to read/write to the db files.

As mentioned in my previous post, the "old method" now fails with an "...
needs updateable query..." error, which lead me to try other methods.

Tried other approaches, still, no joy...

Neil

 

[Arvin Meyer [MVP]]

If your code no longer works, it is possible that there are changes on your
machine, especially if you have done any updates. Assuming there have been
no local changes, the only possibility left is on the server. If you have
Automatic Updates on your machine, try rolling back to a date when you last
knew it worked for sure. If that's not possible, you'll have to work with
your ISP to try and resolve your issue.

 

[Neil Gould]

Hello Arvin,

If your code no longer works, it is possible that there are changes
on your machine, especially if you have done any updates. Assuming
there have been no local changes, the only possibility left is on the
server. If you have Automatic Updates on your machine, try rolling
back to a date when you last knew it worked for sure. If that's not
possible, you'll have to work with your ISP to try and resolve your
issue.

Thanks for your thoughts. Any changes affecting this problem would be on
the server side, e.g. the ISP hosting the site. I was asking primarily to
see if more experienced Access or ASP users had seen this kind of behavior
before.

Best,

Neil

 

[Arvin Meyer [MVP]]

Server security updates to IIS would be my first inquiry. If you can
pinpoint the date when your code stopped working, it will be easier for the
Tech folks at your ISP to narrow down what the problem may be. They should
have a log of all changes. Without knowing more, there's little we can do.

I might also suggest that you post in IIS and ASP newsgroups as they may
have a better idea of current updates.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[Arvin Meyer [MVP]]

Hello Arvin,

I'm coming to the same conclusion that some functions were deprecated with
an "update" to IIS, as everything else is the same on the host. As for
posting the same question in other groups, some folks apparently take
offense to that approach, thinking that a response = an answer, I suppose.

Hi Neil,

Multi-posting in non-related groups is definitely something to avoid, but
cross-posting in a few groups related specifically to your problem, will
only be offensive to the clue-less. Those of us that have been answering
questions for as many years as some of us have, know full well that there
often needs to be further clarification. We also get things wrong from time
to time. The one thing that you can be sure of is that we, as MVPs, will
stick with you for as long as we think we can be helpful.

 

[Neil Gould]

Hello Arvin,

I'm coming to the same conclusion that some functions were deprecated with
an "update" to IIS, as everything else is the same on the host. As for
posting the same question in other groups, some folks apparently take
offense to that approach, thinking that a response = an answer, I suppose.

Thanks for your help!

Neil

 

[aaron.kempf]

From what I've seen of 'needs updatable query'--

a) you build a query
b) your needs change over time
c) you change the query
d) Access throws a tissy-fit and starts thinking that it is too
complex.
e) you're updating against a query; and now all of a sudden-- Access
decides that it is too complex to update in that fashion.

so.. what I reccomend?

f) move to SQL Server or mySql if you don't like an unpredictable
database

-Aaron

 

[Neil Gould]

Hi Aaron,

From what I've seen of 'needs updatable query'--

a) you build a query
b) your needs change over time
c) you change the query
d) Access throws a tissy-fit and starts thinking that it is too
complex.
e) you're updating against a query; and now all of a sudden-- Access
decides that it is too complex to update in that fashion.

so.. what I reccomend?

f) move to SQL Server or mySql if you don't like an unpredictable
database

-Aaron

I use other products for better performance, but this is a case where I
don't have a choice in the matter. Also, I'm interfacing with the Access
data via SQL, not building queries in the application itself, and the
statements are at this point very simple and straight-forward.

Thanks for your thoughts, though!

Neil