I'm considering splitting my DB into FE and BE. The FE will have queries
that create new tables daily, weekly, and monthly (standardized table names
with changing date tags--i.e. Daily03312006, Daily04032006) so the FE is at
risk of growing rapidly. I would like to set up queries in the FE to create
the new tables, export them to the BE then link the newly added BE tables
back to the FE. The part I can't figure out is how to automate the linking
of the new tables to the FE.

Is this a pipe dream or does anyone have suggestions?

=?Utf-8?B?R0JBY2Nlc3M=?= <(E-Mail Removed)> wrote in
news:BED1B7E9-8CC4-4B39-9000-(E-Mail Removed):

> I'm considering splitting my DB into FE and BE.

Don't consider it: do it! <g>

> The FE will have
> queries that create new tables daily, weekly, and monthly

***EEEKK**** oh no... While you are doing your split, you might think
about redesigning to get rid of all these tables too. Store data in
records and in fields, not in table names.


> Is this a pipe dream or does anyone have suggestions?
>

Yes: see above!


Hope it helps


Tim F

I don't know what you are smoking in that pipe, but you are going about it
the hard way.

Rather than creating new tables constantly, all you really need is a date
field in your table that relates to the date of the entry, or whatever is
significant about the date. The just filter all your queries, forms, report,
etc. to include the data for the day, week, month, etc.

This is much better database design, will keep your database from growing
out of control, and really make things much simpler in the long run.

"GBAccess" wrote:

> I'm considering splitting my DB into FE and BE. The FE will have queries
> that create new tables daily, weekly, and monthly (standardized table names
> with changing date tags--i.e. Daily03312006, Daily04032006) so the FE is at
> risk of growing rapidly. I would like to set up queries in the FE to create
> the new tables, export them to the BE then link the newly added BE tables
> back to the FE. The part I can't figure out is how to automate the linking
> of the new tables to the FE.
>
> Is this a pipe dream or does anyone have suggestions?

I certainly appreciate your response and agree with your suggestion. This
particular database is a historical database and the nature of it requires
that day to day status of accounts be kept for research and reporting. It is
not the ideal setup, but the only way I could accomplish the requested
objective with the data provided to me in the manner that it is.

Again, thank you very much for your input.

"Klatuu" wrote:

> I don't know what you are smoking in that pipe, but you are going about it
> the hard way.
>
> Rather than creating new tables constantly, all you really need is a date
> field in your table that relates to the date of the entry, or whatever is
> significant about the date. The just filter all your queries, forms, report,
> etc. to include the data for the day, week, month, etc.
>
> This is much better database design, will keep your database from growing
> out of control, and really make things much simpler in the long run.
>
> "GBAccess" wrote:
>
> > I'm considering splitting my DB into FE and BE. The FE will have queries
> > that create new tables daily, weekly, and monthly (standardized table names
> > with changing date tags--i.e. Daily03312006, Daily04032006) so the FE is at
> > risk of growing rapidly. I would like to set up queries in the FE to create
> > the new tables, export them to the BE then link the newly added BE tables
> > back to the FE. The part I can't figure out is how to automate the linking
> > of the new tables to the FE.
> >
> > Is this a pipe dream or does anyone have suggestions?