OutFront Forums
     Home    Register     Search      Help      Login    

Recent Posts
Todays Posts
Most Active posts
Posts since last visit
My Recent Posts
Mark posts read

Sponsors
Frontpage website templates
Creative Website Templates for FrontPage, Dreamweaver, Flash, SwishMax
Shopping Cart Software
Ecommerce software integrated into Frontpage, Dreamweaver and Golive templates. No monthly fees and available in ASP and PHP versions.
Website Templates
We also have a wide selection of Dreamweaver, Expression Web and Frontpage templates as well as webmaster tools and CSS layouts.

 

Normalizing an Access2K database for FrontPage2K

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
Printable Version 

All Forums >> Web Development >> ASP, PHP, and Database >> Normalizing an Access2K database for FrontPage2K
Page: [1]
 
rogerks2

 

Posts: 2
From: Tucson, AZ, USA
Status: offline

 
Normalizing an Access2K database for FrontPage2K - 3/17/2001 20:16:00   
I have a database full of hotel listings that contain area, city, name, address, phone etc., the usual stuff. Some of the hotels have their own web pages. To enable hyperlinks to these sites I have to devote two columns in the database to allow for these few hotels with web pages. The first field hold the path to a 'link' icon I display using the DRW. The second column holds the URL that is the hyperlink the 'link' icon uses to access the hotel's web site.

There's gotta be a better way.

One approach I was thinking of would normalize these two columns and a unique key field out of the main database. However if this would work, I don't know how to create such a key within FrontPage and I think I'd have to abandon the way FrontPage writes to a database and use SQL to update 2 datatables using a update query.

Any ideas that a beginner could implement?

Spooky

 

Posts: 26630
Joined: 11/11/1998
From: Middle Earth
Status: offline

 
RE: Normalizing an Access2K database for FrontPage2K - 3/17/2001 20:02:00   
For ease of use, I prefer #1 myself.

Using #2, you could then use a Query (access) to supply the info rather than straight from the table.
Rather than try to code the update / creation of new records, Id do it off line in the database.


(in reply to rogerks2)
rogerks2

 

Posts: 2
From: Tucson, AZ, USA
Status: offline

 
RE: Normalizing an Access2K database for FrontPage2K - 3/17/2001 15:30:00   
Appreciate your reply.

I think your right, after all web space is inexpensive.


(in reply to rogerks2)
Page:   [1]

All Forums >> Web Development >> ASP, PHP, and Database >> Normalizing an Access2K database for FrontPage2K
Page: [1]
Jump to: 1





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts