In Backend or Frondend

Djblois

Registered User.
Local time
Today, 14:34
Joined
Jan 26, 2009
Messages
598
I am creating a program now with a front end and back end. In my first program I created the queries in the front end and attached them to the backend within using linked tables. Is this the way I should continue or is it better to created the queries in the backend? If it is then why?

Also, should I create the relationship map in the front end or the back end and why?


I am trying to get better and better at access programing and this knowledge I think will benefit me.
 
Good questions.

I am creating a program now with a front end and back end. In my first program I created the queries in the front end and attached them to the backend within using linked tables. Is this the way I should continue or is it better to created the queries in the backend? If it is then why?
Tables in the back end, everything else in the front end.
If you created a query in the back end then you would not be able to use it without actually opening the back end. Even if you could then you'd be needlessly carrying SQL scripts across the network.

Also, should I create the relationship map in the front end or the back end and why?
The relationships (which are in fact part of the table structure) should be in the back end. If you didn't do this then your data in the back end has no integrity i.e. you could open the back end and add inappropriate data.

Chris
 
Last edited:
1. Queries should be stored in the Front End

2. There is no need to recreate the relationships in the Front End as they already exist in the Back End which is where the data is being stored etc
 
There is one issue with those two questions - they do contradict each other a little bit. When creating the relationships - I need to create relationships not only to the Tables but to Queries as well. So if I build the tables in the back end and then the queries in the front end then I cannot create the relationship in the backend. Does this make any sense?
 
How about not splitting the Database until its complete?
 
Yes, I think I will do that but what about when I do if the queries in the front end and the tables in the back end will force me to create the relationship in the front end wouldn't it?
 
Yes, I think I will do that but what about when I do if the queries in the front end and the tables in the back end will force me to create the relationship in the front end wouldn't it?

Part of the idea of waiting until the database is completed before splitting it, is that if you create the relationships that you require, Access will assist in the splitting process by propogating the relationships wherever they are required.
 
Last edited:

Users who are viewing this thread

Back
Top Bottom