|
If I am using SQL I would either have
everything edited dynamically over the web, using forms to update, create and
edit my records. If I was editing a database locally before showing it to
the world I would create an Access Project and then upload/edit my tables to
change the database information.
Step 3. Create my dynamic page and insert the image
file
In FrontPage I create a page - example: results.asp and
within a database results area I insert ANY photo. Once the photo is inserted I want to now edit the source of the photo
so it shows the database value (in this case the photo column).
| Right-click on the photo and look at the properties of that photo.
Under Picture Source I click browse, and up comes another box allowing me to
look at other photos in the web. I then click on Parameters and choose
insert field value. As long as I am authenticated on the database server
through FrontPage I will then see a list of available columns. I choose
the photo column (see our example) and close. Under the alternative
representations filed - text I type "visit this website" so that once
published when I pass my mouse over the picture there is a mouse over that says
"visit this website". I can also include a hyperlink to another website if you click on the photo if I
fill in the Default hyperlink field (in this case the link field).
This way I get a photo, with a mouseover saying what it is and a hyperlink if I
click on the photo. It looks like a broken photo on your page until it is published and the page
is called up over the Internet with a query something like this: http://www.yourdomain/display.asp?name=John |
![]()
Your photo looks like this until queried over the
Internet |
Inserting hyperlinks is very similar, simply highlight your link and in the
hyperlink dialogue box select parameters, insert field value (example of
table name LINK) and
save. When the page is called over the Internet the right hyperlink
associated with the John Doe record would be returned.
You can also
include dynamic results based on previous queries or cookies and session
variables. Example: http://www.mydomain.com/loginresults.asp?photo=<%=Session("UserName")%>
Email addresses are similar, select database results field, hyperlink,
email and it will show something like this mailto: - just select
parameters, insert field value and you will get something like this when
the page is called up over the internet: mailto:jdoe@aa.com.
The database included the email address in
the right place based on the query.
What is happening is that instead of having to
code all of this yourself, FrontPage is filling in its own ASP code that
tells it what to do. An example of this would be:
<%=FP_FieldHTML(fp_rs,"photo")%>
|
