Thread: Chapter 15!!
View Single Post
  #8 (permalink)  
Old March 9th, 2004, 10:07 AM
Imar's Avatar
Imar Imar is offline
Wrox Author
Points: 72,055, Level: 100
Points: 72,055, Level: 100 Points: 72,055, Level: 100 Points: 72,055, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,086
Thanks: 80
Thanked 1,587 Times in 1,563 Posts
Default

What you posted in your previous message is how you open the connection; not how you create the connection object. You probably have something like
Set objConn = Server.CreateObject("ADODB.Connection") in your code, which is how it's supposed to be. Are you sure server.mappath("\goinggoinggone\db\Classified_2000 .mdb") results in a valid path to the database? That is, does the current root of the site have a goinggoinggone folder?

If you get the "the page cannot be displayed" error, you may need to turn off friendly error messages. In Internet Explorer, open the Advanced tab of the Options dialog, and uncheck "Show friendly HTTP error messages". For your Web site in IIS, open the Properties dialog, switch to the Home Directory tab, and click the Configuration button. On the Debugging tab, make sure "Send detailed ASP error messages to the client" is checked.
Then run the page, and see if you get any error information.

What I meant with testing in access: copy the SQL statement you posted here and paste it in a new Access Query. For this to work, you may need to switch to SQL View of the Query Designer. What happens when you run the code there? Is the record inserted correctly?



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.