modify split Access database

Hi Experts
i created an access application using access 2013,
i split the database to back end  App_be.accdb and front end App.accdb,
then i converted the front end to an App_be..accde to secure the VBA code,
i shared the App_be.accde application with the users in shared drive including the back end tables App_be..accde.
I moved   App.accdb to my pc.
now the owner request some modification to the application, so i wen to edit the   App.accdb that available in my local computer. but i keep getting this error
'g:\shared\App_be.accde' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides

do i have to copy App.accdb to the shared drive to be able to work on it? or there are another way to modify the application?
and after modification, do i have to again change the application to accde?
can i modify the accde file directly?

can you please help me with this
LVL 1
AZZA-KHAMEESAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rey Obrero (Capricorn1)Commented:
- can i modify the accde file directly?
NO, you have to modify the .accdb file and create an .accde file after the modification

- do i have to copy App.accdb to the shared drive to be able to work on it?
NO, it is better to work on the development and modification of the app that is running locally.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<'g:\shared\App_be.accde' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides>>

 You need to relink the tables with the Linked Table Manager.....all the table links are pointing to the BE.

 When your working on the app locally, you'll need a copy of the FE and BE and will need to relink.  Then before distributing back to the users, you will again need to relink the tables back to their BE.

Normally, most developers add this in to happen automatically in some form (there are numerous utilities and code for handling linked tables floating around).

Jim.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dale FyeOwner, Developing Solutions LLCCommented:
Generally, I would advise you not to use mapped drive letters when linking to your tables, but the actual fully qualified path to the backend.  Use the Linked TAble manager to do this by instead of selecting the drive letter, enter the UNC path, this would look something like:

\\servername\shared\app_be.accdb

You really are not going to improve security of the backend by changing the accdb extension to accde.

You indicate above that you changed the name of the FE to app_be.accde?  Did you mean app.accde?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.