GUI using Access 2002 1

[Gabsterr]

Hello everyone,

I have a database in Access 2002 and I need to set up a frontend/GUI/whatever that does the following:
When a hotspot on the flowsheet (VERY LARGE jpeg) is clicked, it needs to display all of the information about that item (which could be any record [aka. row] from the database) in a sidebar. There will likely only be one user at any one time, and the user will have access to the folder where the database is stored. There are about 150 items.

I have been unable to do this with Access 2002, so I doodled around a bit trying to export it to XML and using Javascript, but the need is for a dynamic interface, not one that needs to be updated every time a change is made. I have a suspicion that ASP is involved in the solution, but I know practically nothing about it.

I haven't been able to find any literature on the subject, so any tips/links/advice/whatever is greatly appreciated.

Thanks!

 

[fneily]

For future reference, "I have been unable to do this with Access 2002," doesn't tell us anything. What exactly was the problem, error messages, your code, etc.

You might want to see the following on how to set up "hotspots":
thread702-1489846

Then on the OnClick event, have it run a query to filter the table and display the data on a subform or listbox or however you want to present it.

No need for ASP. Just regular VBA and Access.

 

[Gabsterr]

My apologies fneily, I should have been more clear as to the specific issue.

I have been unable to create a front end like the one I described using Access 2002. I have looked both in the Help files and on the web, and have found nothing on how to do that in Access 2002.

I have written a script in JavaScript for the hotspots and the display, but have been unable to link it to the database itself and I resorted to exported XML files for testing.

The things I am trying to link to are contained in several different tables. I have not a single clue how to create something that looks in all of the tables in the database for the number "3631" in a field called AssetID.

I am looking for info/links/pointers/help on either
(1) a way to link the Access database directly into such a JavaScript page, or
(2) a way to create a page in Access 2002 itself that has such functionality

Attached is a picture of what I have now (roughly what I want the GUI to look like. When the area over an equipment is clicked, the info appears at the bottom of the page (I haven't gotten it in the proper spot yet, but I hope that this will become irrelevant).

Just to clarify, the different types of equipment are in different tables, but all have "AssetID" asprimary key.

Humbly grateful,
Gabe

 

[fneily]

I need to ask more questions. Are you on a shared drive of an INTRAnet? Or are you on an INTERnet? From your first description, it sounds like a shared drive. If so, you don't need any web page, just a regular form.
Are you having troubles splitting the database? Are you using the Database Splitter?
How many users? If 10 or less, they can just go directly to the database on the shared drive without any problem so you don't need a FE/BE.
Are you trying to create DAP's (Data Access Pages)?

Finally, it doesn't sound like your tables are normalized. "Just to clarify, the different types of equipment are in different tables, but all have "AssetID"" You should only have one tblEquipment. If all you have is 150 items, redesigning won't be that bad.

Post your table(s) structure: eg.
tblCustomers
CustID Primary Key
FirstName
Phone
Etc.

If your tables aren't normalized, creating a web page will be quite a bad task.

Have you seen:
Fundamentals of Relational Database Design

http://r937.com/relational.html

 

[Gabsterr]

I am on an INTRAnet, I have used the database splitter, there will be less than 10 users.

More importantly though, you are right: the database is most definitely NOT normalized. Turns out it was set up like a "linked Excel spreadsheet". It is 1NF but not 2NF.

I was trying to set up the page for a non-normalized database without realizing that it would be less work simply to normalize said database.

There is restructuring to be done!!!
(certainly before I try to do this again and/or bother you wonderful people)

fneily, thanks for your understanding, and for not biting my head off