Best way for intranet db using data pages and hyperlinks?

[ljjtek]

We have a very large amount of pictures that are stored on our local server. I am attempting to make a database so that I can create a local data page that people can type in key words and get matching files... The database itself is fairly simple in structure but I'm running into problems. I have one table which has 3 fields, ID, LOCATION, KEYWORDS. I then have a query that simply asks for the keywords and then returns records based on that. Ideally I would like for people to be able to click on the file and be able to insert the picture that they want, into the word doc or email that they are sending but I'm not sure how to do this.

I had the LOCATION set up as a hyperlink in the table and when I run the query in access it works, but when I make a data page it returns un unclickable link.

If my ultimate goal is to be able to have people be able to insert the pictures that they want from the results of their search, is this the best way to do it? Would I be better off if I moved all the pictures from regular folders and put them all in the db itself? There are a couple thousand pictures so it would be a huge db which is ok, if this is the best way to do it. Someone mentioned to me something about 'drag and drop' abilities....anyone have any suggestions?

 

[Dimandja]

Storing pictures inside the DB is the worst of all worlds - not recommended - keep them away in those folders.

Looks like you're almost there: "I had the LOCATION set up as a hyperlink in the table and when I run the query in access it works, but when I make a data page it returns un unclickable link. "

Now, all you have to do is tell us how you "make a data page and return a link into it", and someone may be able to help.

Oh, and what database/language were you trying to do this in/with?

Dimandja

 

[CajunCenturion]

Since you seem to be asking for a consensus, I will then echo the sentiments of Dimandja. I find it preferable to store the pathname in the database, but keep the image outside as a stand-alone file.

Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[ljjtek]

Looks like you're almost there: "I had the LOCATION set up as a hyperlink in the table and when I run the query in access it works, but when I make a data page it returns un unclickable link. "

Now, all you have to do is tell us how you "make a data page and return a link into it", and someone may be able to help.

Oh, and what database/language were you trying to do this in/with?

Well perhaps I'll explain what I'm trying to do and that will help... We have a lot of pictures on our local intranet and I want to make a database that stores the location of the picture (thanks for your opinions on storing vs linking btw) along with key words that would be used in searching for the pictures. So for instance someone would type in 'blue' and it would query the db and bring back all records that have 'blue' as a keyword. That part I can figure out, and I can even get the link to work... but what I can't get to work is making a data access page to load to our intranet that would allow for the query and clickable links. Right now it gives me either this:

#..\Pictures\2_04\P1010005.JPG#

which obviously isn't clickable, or it gives me nothing.

I have the location set as a hyperlink in my table, just fyi.

Being that I've never made an access data page before I thought I'd take the simple route and use the wizard, which is how I made it...simply made a query and then used that query as my source for the data page. Obviously I'm doing something very wrong here but I didn't think that this part of the project was going to be the hardest.

I appreciate any feedback that you can give me and have already made the better choice in where I'm keeping my actual pictures, so thank you in advance!

 

[ljjtek]

Sorry for the cut-paste at the top...that's what I get for not previewing my post....;-)

 

[dcusick]

Just a little uggestion... I could be wrong on this one, but you would have, I assume, multiple Keywords for each file. I would also assume that different files could have the same Keywords. Whey don't you normalize your DB, by splitting off the keywords field into a seperate table. Make your Pictures table have { ID, Location } and then have a keyword table that has { ID, Keyword } and then a relationship table { ID, LocationID, KeywordID }. This way, you can have multiple keywords for each file, and multiple files can have the same keywords... Plus if you have to change a keyword that appears in multiple files, you only have to do so once! Like I said, this might be overkill for what you're trying to do, but I think it'll cut down on your maintenance in the future. Either way, best of luck!