By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,968 Members | 1,178 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,968 IT Pros & Developers. It's quick & easy.

Back End/Front End Puzzle

P: n/a
Hi:

I have an application that has a back end and a front end. I need to add a table which is
identical to one in the back end, and then use it for a temporary holing place form some
records. I have done the following:

.. Copied the table in the back end and given the copy a new name
.. Created a table with the identical name to the back end copy in the front end
.. Used the linkage process to link the table reference in the front end with the new
table in the back end.

Changes to the two table are indepnedent if I am just yusing the "back end", but whe gthey
are executed from the "front end" references to the new table also appear to cause
changes in the original back end table. So for example if I try and empty the temp table,
the original table is also emptied. This is not something that is supposed to happen.

Can someone give me the steps required in a back end/front end situation so that a new
table can be created from an original table, and then linked from the front end to the
back end?

Id appreciate It.

John baker
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
John Baker wrote:
I have an application that has a back end and a front end. I need to add a table which is
identical to one in the back end, and then use it for a temporary holing place form some
records. I have done the following:


Why is it necessary for the tables to have the same name? It seems like
a dangerous situation that should be avoided if it could at all be helped.

Nov 13 '05 #2

P: n/a


Sorry.. I didnt make myself clear. the sturcture of the tables will eb the same, the namse
clearly will be different. MasterTransactions Temp will be one and MasterTransactions will
be the other.
John Baker wrote:
I have an application that has a back end and a front end. I need to add a table which is
identical to one in the back end, and then use it for a temporary holing place form some
records. I have done the following:


Why is it necessary for the tables to have the same name? It seems like
a dangerous situation that should be avoided if it could at all be helped.


Nov 13 '05 #3

P: n/a
John Baker <Ba******@Verizon.net> wrote:
I have an application that has a back end and a front end. I need to add a table which is
identical to one in the back end, and then use it for a temporary holing place form some
records. I have done the following:

. Copied the table in the back end and given the copy a new name
Did you delete the link to the old table name in the backend?
. Created a table with the identical name to the back end copy in the front end
Use a temporary MDB instead of the FE as this will lead to bloating.

See the TempTables.MDB page at my website which illustrates how to use a temporary
MDB in your app. http://www.granite.ab.ca/access/temptables.htm
. Used the linkage process to link the table reference in the front end with the new
table in the back end.

Changes to the two table are indepnedent if I am just yusing the "back end", but whe gthey
are executed from the "front end" references to the new table also appear to cause
changes in the original back end table. So for example if I try and empty the temp table,
the original table is also emptied. This is not something that is supposed to happen.
Why not just create your temp table new each time? Others will suggest you keep a
copy of the temp MDB and copy it across as required.
Can someone give me the steps required in a back end/front end situation so that a new
table can be created from an original table, and then linked from the front end to the
back end?


The above temp tables MDB will give you a starting point.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 13 '05 #4

P: n/a
Tony Toews <tt****@telusplanet.net> wrote:
John Baker <Ba******@Verizon.net> wrote:
I have an application that has a back end and a front end. I need to add a table which is
identical to one in the back end, and then use it for a temporary holing place form some
records. I have done the following:

. Copied the table in the back end and given the copy a new name


Did you delete the link to the old table name in the backend?


NO -- I DID NOT REALIZE THAT THERE WAS A LINK. HOW DO I REMOVE IT?

THIS IS THE PROBLEM IM CERTAIN!
. Created a table with the identical name to the back end copy in the front end


Use a temporary MDB instead of the FE as this will lead to bloating.

See the TempTables.MDB page at my website which illustrates how to use a temporary
MDB in your app. http://www.granite.ab.ca/access/temptables.htm
. Used the linkage process to link the table reference in the front end with the new
table in the back end.

Changes to the two table are indepnedent if I am just yusing the "back end", but whe gthey
are executed from the "front end" references to the new table also appear to cause
changes in the original back end table. So for example if I try and empty the temp table,
the original table is also emptied. This is not something that is supposed to happen.


Why not just create your temp table new each time? Others will suggest you keep a
copy of the temp MDB and copy it across as required.
Can someone give me the steps required in a back end/front end situation so that a new
table can be created from an original table, and then linked from the front end to the
back end?


The above temp tables MDB will give you a starting point.

Tony


Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.