Link to home
Start Free TrialLog in
Avatar of jana
janaFlag for United States of America

asked on

Consideration when creating views in an existing Microsoft Access database

We have a database in MS Access.  This DB has over 100 tables and lots of views.  This DBs' apps is about to go thru some required changes by users.

For what we need to do, the DB hasn't direct table relationship within it's structure (by this we mean a lot of child tables has no parent id being referenced) to produce the result required. 

We decided  to create views.

Our main concerne is the DB current structure and what impact will addtional views implies?  We don't want the application to be affected by the modification so the report is created in a new apps and will be linked by clic from main apps.  The o ly modification that's going to be done are new views.

Please advice
Avatar of Scott McDaniel (EE MVE )
Scott McDaniel (EE MVE )
Flag of United States of America image

A view is just a subset of data that may include one or more tables (assuming we're talking about SQL Server views, that is). It cannot impact other tables or views, since it's just pulling data from the source tables.

So if all you're doing is ADDING new views, then you really cannot affect existing views.

Obviously you could impact existing data if you perform data actions against the view (update, delete, etc), but I don't think that's what you're asking.



Avatar of jana

ASKER

We are working with Microsoft Access, not MS SQL.

Please advice
Try to recreate the issue using 3 tables and attach the database.
Include few records in each table and show the required output.
Define what you mean by "views" ... there's really no need to upload a database for a question like this.
ASKER CERTIFIED SOLUTION
Avatar of Jeffrey Coachman
Jeffrey Coachman
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jana

ASKER

You guys may be right.  I don't think us called "views" in Access (we were thinking of SQL).

I'm not at the computer, but I think it's queries.

Based in this, we so have lots of saved queries.  We just want to have an opinion of what shoul we consider when creating more queries when the access table is already filled with lots of queries.


Our main concern is if we create new queries any existing tables or queris be affected negatively I'm any way?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jana

ASKER

Great Info!

Ok, we need to develop a report, not for a Form that will consist of 5 tables.  By form we mean a inquiry screen or data entry.

    - In order to print the report successfully, we'll start all queries from fresh, not from
      existing queries.
    - The access to the the DB is only via apps, not on the DB, so users can't access
      directly on the DB.
    - Finally, the report is not complex, so we think the term "Non-Updateable" should
      not be a concern.

Going about this way, would be ok to proceed?

SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jana

ASKER

Thank you very much.

Just to close the question, is it safe to say that MS Access has no type of "view" tables as in MS SQL?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jana

ASKER

Thanx