Can't Connect to Database (ACCESS.mdb)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can't figure this one out. I have an access.mdb on my hosting site. It is in
a subfolder called "/fdb" .. Using the DRW, I create the table for the
query - it even displays the fields properly for my selection.

When I launch the published site, I get an HTTP 500 Internal Error - and it
tells me to refresh the page .. which of course doesn't work. I *know* the
database is fine on the site as my Admin maintenance and updating works
perfectly ... I just can't get this darn FP interface to View and Display the
results in it.. and it's set READ/WRITE access ..

Any ideas??
 
This is a remote web site ... It's my main Site hosted ... Users are able to
READ/WRITE to the dataqbase (their user information & registration) just
fine. When I launch a Web Page to view the information as part of DRW, I get
that failure. Thanks Steve..!
 
Make sure that the IUSR account has the proper permissions. A lot of people
make the mistake of assigning individual users with permission, but ASP uses
the IUSR account for most activities so this could be where the error comes
from.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
I have a ticket into support to check this ISUR issue... But to be clear,
users are able to update their registration information just fine ... Why
would they be able to do that and yet not be able to connect to the DB ?
(Nor can I for that matter when I launch the page. I get the same error as
ADMIN to the site.) I'll post what I find out form my HOSTing service.
 
Just confirmed (and saw with my eyes) - the \fpdb directory which contains
the database is "allowed" ... I do NOT have specific user access rules.

Any other ideas? I can let you see the problem if you want.... however I
need to add an id & pw for you.

Thanks
 
I have had this problem several times and the problem was not always the
same. To begin with check to see if you have "Timestamp" in your table. It
gets created by default using the DRW. It will cause the database to error
out when trying to view the results.. I suggest that you open the database
and the "Results" table and delete the field named :Timestamp" then post to
the server and try again.

Note: there is a way to go into the view procedure and fix that, but if you
do not use or need the timestamp, then this will probably fix it. If you need
the time stamp you can go to the knowledge base and find the exact way to
work around the problem. It is basically a matter of finding the word
"Timestamp" in the query and putting brackets around it.
 
Can't figure this one out. I have an access.mdb on my hosting site. It is in
a subfolder called "/fdb" ..
Click to expand...

You mean fpdb , correct?
When I launch the published site, I get an HTTP 500 Internal Error - and it
tells me to refresh the page ..
Click to expand...

Are you saying when you try to view the site in your browser, you cant
even see the default page of your website? Or are you talking about
what happens when you try to view a page that has database results on
it?
 
This is wierd. I had the database reults table embedded in a table of a new
page that was created form a Tempate (dwt). I decided to just delelet the
page and create a new page - not from a template - just a blank page with the
inserted DRW results. Works fine ... now I need to figure what it is about a
template that created this problem.. At least it's working now.

Thanks all.
 
Yes - \fpdb is what I meant to type.

I was trying to say that the RESULTS-only page of the DRW results - when I
clicked on that page, I received an HTTP 500 error. However see my other
post. This appears to be something to do with a TEMPLATE that I embedded the
DRW results into. Once I created the DRW results in a blank page, it works
fine... I;m trying to now figure out what it is about TEMPLATES that
introduced this.

Thanks
 
Yes, I have found that attaching DWT's to asp pages (ASP pages in general,
not just the FP DB components) seems to erased some of the ASP
code....annoying!
 
Back
Top