i have a low budget site that runs an access database. the db is updated weekly and uploaded from the local machine. however the db is quite large and several tables are not used by the website as such, they are for local admin,
could i just export the tables that are used by the website into a new db and upload that without setting up the relationships again, or do the relationships form part of the neccesairy structure, i'm using ASP to call the database and the tables are related like catagory > product etc. but i'm thinking the SQL used to call the db bypasses the need for the tables to be related formally eg if SELECT Catagory from products where catagory = widget will bring up all widgets from the products table anyway, do i need to have formally stated the relationship between the 2 within the db or am i misunderstanding how access works... or have i just gone tooo long without sleep?
Well, it's 2 o'clock in the morning as I write this so I must have some semblance of compassion for the bleary-eyed . . .
Please do not be disheartened here but your Q is SO specific. I have done work in MS Access and I do understand the general flavor of your request, but I cannot reply to the specific. Most who frequent probably feel the same way.
There is a Site Search feature here which often is overlooked (top left side of the upper portion), search on "access database" for some responses to earlier queries which may point you in a good direction. (You will get a half dozen discussions which may be helpful.)
There is no need to have the relationships in place, in order to run the queries against the DB.
Of course, it is much better practice to have them. And also you will lose any cascading delete functionality between parent and child tables.
However, for SELECT queries, you will be ok. I would also suggest compressing the new database (via Access, not something like .zip) after you have exported the tables to the new database. This should help save your filesizes.