fe/be question

  • Thread starter Thread starter JohnE
  • Start date Start date
J

JohnE

I have a A2k database that is on one of the Citrix server
and it is split into the fe and be. It is working fine
within a multi user environment. My question is when I
am updating the front end. I make a copy of the front
end and leave it on the server. I also have a
development copy (unsplit)on my harddrive. I would like
to continue using the one on my harddrive for continuing
updates, etc to the front end. I can copy and paste the
unsplit copy into the folder on the server and then split
it. If I delete the development_be, the front end tries
to read the deleted development_be. I tried to link the
tables for the real backend and end up with 2 sets of
tables in the development front end. Where can I go to
change the path of the initial linked tables (now
deleted) to point them to the real tables? Would a
simple file name change work? If so, which one (fe or
be) would get changed? I prefer not to work on the copy
that is the copy of the real front end that I left on the
server if possible. When I work on the development copy
on my harddrive, I can enter any type of info for testing
the change and not having worry about screwing up the
real thing. I hope I explained it good enough to
understand.
Any suggestions out there? I'm abit new to this fe/be
thing.
*** John
 
Please ignore this question. I finally got it figured
out with Linked Table Manager.
Thank you for your time.
*** John
 
JohnE said:
I have a A2k database that is on one of the Citrix server
and it is split into the fe and be. It is working fine
within a multi user environment. My question is when I
am updating the front end. I make a copy of the front
end and leave it on the server. I also have a
development copy (unsplit)on my harddrive. ....
Where can I go to
change the path of the initial linked tables (now
deleted) to point them to the real tables?
I prefer not to work on the copy
that is the copy of the real front end that I left on the
server if possible. When I work on the development copy
on my harddrive, I can enter any type of info for testing
the change and not having worry about screwing up the
real thing.
Click to expand...

-John, I understand your need to work with another datasource than the
real BE when developing. I suggest you use split FE/BE also when
developing, then change linkedTable reference in FE to BE on net
before distributing.

First, make a copy of the current FE and BE to your local drive, then
open the local FE, Tools-AddIns-LinkedTableManager,
SelectAll/AlwaysPromptForNewLocation, and give new table location =
local BE.
Then you develop locally. When distributing, make a copy of your FE,
and use LinkedTableManager to change its references over to network
BE, and distribute this FE.
-I use Acc97, but Acc2k should be similar.

Thor Ivar Hellesoy, Norway
 
Back
Top