Front End vs Back End

  • Thread starter Thread starter JethroUK©
  • Start date Start date
J

JethroUK©

i've put a lot of work into my forms/reports and i want to protect &
seperate them from the main data tables

if i split the databse in two - should i leave the queries with the tables
or move the queries to the front end with the forms/reports (assuming i have
a choice)
 
Query solved - I've just found a built-in splitter (after i'd already split
it) - it puts queries with the front end stuff
 
JethroUK© said:
Query solved - I've just found a built-in splitter (after i'd already
split it) - it puts queries with the front end stuff
Click to expand...

If you want the queries with the tables you can open the backend and import
them then link them from the front end. I've looked at a couple of
commercial applications built on Access mdb files and have seen them done
both ways.
 
i've put a lot of work into my forms/reports and i want to protect &
seperate them from the main data tables

if i split the databse in two - should i leave the queries with the tables
or move the queries to the front end with the forms/reports (assuming i have
a choice)
Click to expand...

The tables go in the backend. EVERYTHING else goes in the frontend.

John W. Vinson[MVP]
 
John said:
The tables go in the backend. EVERYTHING else goes in the frontend.

John W. Vinson[MVP]
Click to expand...

I have a question John about this. I've looked at several commercial
programs using mdb file structure and about half have the queries in the
back end. I was just wondering what the advantages are to either setup. I
did notice that with an mde file queries can be added and edited but
reports, module, forms can't.
 
Joe Cilinceon said:
I have a question John about this. I've looked at several commercial
programs using mdb file structure and about half have the queries in the
back end. I was just wondering what the advantages are to either setup. I
did notice that with an mde file queries can be added and edited but
reports, module, forms can't.
Click to expand...

i assumed mde compiled forms/report/code/modules - but you cant compile
tables/queries

i'm not sure of benefits/disadvantages with the queries (hence the
question) - but the splitter put them in the front end, so i assume thats
the best place
 
I'm kind of curious about the advantages and disadvantages of both methods
myself.


JethroUK© said:
Joe Cilinceon said:
I have a question John about this. I've looked at several commercial
programs using mdb file structure and about half have the queries in
the back end. I was just wondering what the advantages are to either
setup. I did notice that with an mde file queries can be added and
edited but reports, module, forms can't.
Click to expand...

i assumed mde compiled forms/report/code/modules - but you cant
compile tables/queries

i'm not sure of benefits/disadvantages with the queries (hence the
question) - but the splitter put them in the front end, so i assume
thats the best place
Click to expand...
 
Joe Cilinceon said:
I'm kind of curious about the advantages and disadvantages of both methods
myself.
Click to expand...

Queries are executed in the FE. What you are describing as "queries" are just
the saved definitions of queries. If stored in the BE the FE will have to pull
those definitions over the network before it can execute them. All this
accomplishes is needless network traffic. I can think of no advantage to
putting the queries in the BE.
 
Rick said:
Queries are executed in the FE. What you are describing as "queries"
are just the saved definitions of queries. If stored in the BE the
FE will have to pull those definitions over the network before it can
execute them. All this accomplishes is needless network traffic. I
can think of no advantage to putting the queries in the BE.
Click to expand...

Thanks Rick, I was wondering since the #1 program in my field does just
that. However it isn't a network setup but on 1 computer system.
 
Joe Cilinceon said:
Thanks Rick, I was wondering since the #1 program in my field does just that.
However it isn't a network setup but on 1 computer system.
Click to expand...

Well in a split app deployed on a single PC the only real thing you are gaining
by splitting is the ability to easily update the front end simply be replacing
it without disturbing the data in the back end. Here again there is nothing to
"disturb" in a query definition and a front end upgrade could very often require
new and/or changed queries. These also seem to point to the front end as their
logical location.
 
Thanks Rick, I was wondering since the #1 program in my field does just
that. However it isn't a network setup but on 1 computer system.
Click to expand...

No, likely does not do the above. If you do have a split database, then how
does the front end use, or execute queries in the back end?
(answer: you can't link to those queries, and you can't "see" them in the
front end).

The only reason why I can think of some queries in the back end is that they
are there for maintenance type stuff, or are not actually used. They also
could possibly be used if/when the back end is opened via automaton, but I
doubt that.

It is also possible they are "copied" on occasion from the back end to the
front end.

If you on occasions open up the back end for types of maintains, then those
queries can be used.

However, how can you use queries in the back end when you launch the front
end? You have to explain this to me, or what you say don't make sense?
 
Albert D.Kallal said:
However, how can you use queries in the back end when you launch the
front end? You have to explain this to me, or what you say don't make
sense?
Click to expand...

I suppose you could open a separate connection to the back-end (using
OpenDatabase in DAO, or via an ADO Connection object) and execute them
that way. But it's not clear to me what the point would be.
 
People who don't have their application stored in
a database (like we do) still have to find somewhere
to store their queries.

They can store them as text in the executable.
They can store them as text resources in the executable.
They can store them in the same database where their data is stored.

Storing your queries in the same database where the
data is stored is often better than storing them
as text in the executable because

1) You can update the queries separately from the executable.
2) The queries hide the database internals from the executable.
3) The queries can be precompiled and optimised in the database.

You can partition your application into three (or more) layers:

Forms
Business Logic (queries)
Data

If you want to have a two layer system, you can make
a decision about where you want to place the middle
layer. You can even split the middle layer if you
want, with some queries in one place and some in
the other:

First the architecture implications:
VB6 + SQL Server = queries in database

Then the coding practice decisions:
VB6 + database = queries always in the same place for both MDB and SQL
Server

And the performance implications:
SQL Server = queries in BE database
Access MDB = queries in FE database

And the application development logic:
Frequent changes = stored with frequently changing stuff
Infrequent changes = stored with static stuff

So if your database structure was frequently
changing, you would naturally put queries there
so that your application didn't have to change
at all.

(david)
 
I was looking at the demo of the app again and to be honest I've never paid
any attention to the front end (exe file). I would assume that is it
probably written in some other such language and just uses the access file
structure for its tables. I never paid much attention to the front, as I
was more interested in their table design and relationships.
 
That's the point exactly, Joe. When the 'front-end' application is an Access
application, there's little if any reason to have queries in the 'back-end'
data MDB. But if the application is *not* an Access application, then there
are good reasons to save queries in an MDB.
 
Brendan Reynolds said:
That's the point exactly, Joe. When the 'front-end' application is an Access
application, there's little if any reason to have queries in the 'back-end'
data MDB. But if the application is *not* an Access application, then there
are good reasons to save queries in an MDB.
Click to expand...

Yes the "point" changes entirely when the front end in not Access.
 
Thanks Brenden & Rick for the explanations. I'm just trying to get a handle
on the why's of this.
 
Back
Top