When it comes to the immediate problem that we can't solve, we're all
dummies. Once the problem is understood and solved we're geniuses
again.
The most common issues that arise in the manipulation and management
of split Access applications during development are those to do with
the proper synchronizing of *each* FrontEnd with its respective
BackEnd. Specify the path name of each component. Be unambiguous
about referring to each part. Try something like FE1 and BE1 and FE2
and BE2
It would be helpful if you were to specify what happened with each of
the parts of both copies of your applications. If you do that, you
might discover and resolve the problem and solution on your own.
Since I can't see your computer, I don't really grasp what the
symptoms actually are. I speculate that something like this went on:
You split your application using the provided tool or from advice
garnered here. Once you verified that the original application worked
it its new configuration, you copied it into a new folder or renamed
the FE and BE and left it in the same folder with the original.
However, you didn't mention if you want the new application to operate
as a completely different application from the original or simply as a
new FE that happened to be located elsewhere or named something else.
My guess is that you are trying to create something that you can dress
up and then give to others.
If the latter just above is what you want then in FE2;;
Tools/AddIns/Linked Table Manager and check the box that says "Always
ask me" & click OK. When the new dialog box opens for the first
table, navigate to that table in BE2 and click OK. That should find
all of the tables. Without clicking "Ask Me", click OK and you're
done.
Now, entering data into the forms in FE2 will cause that data to
appear in BE2. Each session will cause the date on BE2 to change.
FWIW I have an application that I created back in the mid '90s. It's
really handy for tracking project elements. When I start a new
project, I create and re-name a new copy of the app for the new
project. Probably one time in ten, I forget to re-link the tables
until after I've emptied the tables of the last project's data and
began tracking the new project. Fortunately I have an automatic
backup for my Access files.
HTH
>> Stay informed about: Access 2003 not Updating Date on MDB File in Vista OS Envi..