cannot be read; no read permission on table in Access

[Guest]

I apologize to start for the forecoming long explanation of the problem. I
have an Access 2000 database that contains data about the properties in town.
I'm new at FP2000, ASP, etc; but have experience with VBA. In starting the
development effort I created a copy (subset) of the town database and
imported it into FP. I've have created a number of ASP pages that access the
subset database OK; however I have the DB connection code in each of the
pages. I have started to pull the code out of the ASP pages and making the
connection via an include file (right thing to do especially since my future
Host will have the DB in a different directory name than FP recommended
directory). I've tested the code in one of the pages and everything seems to
work OK. So the next thing I did was to import the full town database into FP
using the import option after opening the web with the "open web" method. The
import was OK and I then used the tools/web option/database menu to verify
the larger DB (kept the subset there also). The full DB shows as verified.

If I change the include file to the full DB name and run the one ASP page
I'm testing; I get an error when it hits (1st sql) the "Set
rssk=conntemp.execute(SQLsk)" line in the test ASP page that queries a file
in the DB named "system_control". The error message reads:

Microsoft JET Database Engine (0x80040E09)
Record(s) cannot be read; no read permission on 'system_control'.
/ASP/land.asp, line 48

Both DB are password protected, both DB have the rights to the table set for
all rights. The subset DB works in both "hard coded" and include file
senerios. The full DB does not work in either case.

It appears I must have missed a step in setting up the full DB. Is there
something in IIS I need to do or ???

Thanks
Jim T.

 

[Mark Fitzpatrick]

Check for the permissions that exist in windows itself. The error you are
getting could have nothing to do with the passwords that are within access,
but for the windows account that the OS uses to access the db. By default,
the IUSR_machinename account (internet user anonymous account, format is
IUSR_ followed by the name of the computer) does not have write access to
files. When you imported the database FP imported it as a normal file
probably. This means it doesn't have the permissons on it. One of the
reasons that FP creates directories such as _private abd _fpdb is to have a
place that has write permissions. You can either set the file permissions
for this file manually through Windows Explorer, add the IUSR account if not
present, and give the IUSR account Write permissions, or try placing it
within the _private directory or another write-enabled directory.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage