I would definately store that info in a table. Administration is much
easier and so is dealing with the controls themselves.
I actually do something similar on a site and it works well. Just in
case it's applicable, here's what I do there:
1. Two lookup tables, one stores a list of departments and the first
half of a page name, the other stores areas in those departments and
the second half of the page name.
2. The user selects a department.
3. The user selects a work station and clicks Go. At that point, the
first and second half of the page names are combined, and the correct
page is accessed.
This allows me to store a lot less in my tables to access my 300+
pages as I don't have to account for every combination of department
and work area. I don't know if your 1000+ links can be broken down
this way, but I thought I'd throw it out there in case you could use
it. Maybe limiting choices in the second drop-down rather than having
20 different pages to start from? Hope this helps.
-Josh
th**************@aol.com (phil) wrote in message news:<37**************************@posting.google. com>...
We are developing specs. for a website for a nonprofit org, with
database for membership related functions.
But..question is regarding drop down menu links. We will have 20
category-pages, and each page will have 30-50 links- unique to that
page, so 1000+ total for site- on a drop down menu. Need we assume
that such links (both plain english description to appear on site, and
actual URL to link to- so 2 pieces data really for each link(?)) are
stored in a table on site or in our main database, or are they somehow
embedded into each menu on individual pages. We will have an admin
area allowing us to change them in either event, I assume, but we just
want to know if we must design in storage and search for such link
info in main database. Either Access or SQL. Thanks.
