Front End vs Back End

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©" wrote in message
...
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)

JethroUK© wrote:
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©" wrote in message
...
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)

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.

--

Joe Cilinceon

On Wed, 16 Nov 2005 22:00:11 GMT, "JethroUK©" wrote:

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)


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

John W. Vinson[MVP]

John Vinson wrote:
On Wed, 16 Nov 2005 22:00:11 GMT, "JethroUK©" wrote:

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)


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

John W. Vinson[MVP]

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

"Joe Cilinceon" wrote in message
...
John Vinson wrote:
On Wed, 16 Nov 2005 22:00:11 GMT, "JethroUK©" wrote:

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)


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

John W. Vinson[MVP]

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.


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
--

Joe Cilinceon

I'm kind of curious about the advantages and disadvantages of both methods
myself.


JethroUK© wrote:
"Joe Cilinceon" wrote in message
...
John Vinson wrote:
On Wed, 16 Nov 2005 22:00:11 GMT, "JethroUK©"
wrote:

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)


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

John W. Vinson[MVP]

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.


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
--

Joe Cilinceon

--

Joe Cilinceon

"Joe Cilinceon" wrote in message
...
I'm kind of curious about the advantages and disadvantages of both methods
myself.

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.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Rick Brandt wrote:
"Joe Cilinceon" wrote in message
...
I'm kind of curious about the advantages and disadvantages of both
methods myself.

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.

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

"Joe Cilinceon" wrote in message
...
Rick Brandt wrote:
"Joe Cilinceon" wrote in message
...
I'm kind of curious about the advantages and disadvantages of both
methods myself.

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.

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.

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.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com