Changes in accde not reflecting in source

[jobbie]

I have created an accde file and saved it on my desktop. This file has some forms in it. One of the forms is linked to a table using query builder. When I updated the table using the form in the accde file it doesn't reflect in the source database but the records show up in the form in the accde. Now I am afraid if I were to make changes to the source and create a new accde it won't reflect the updated records of the accde.

[orange]

Please provide some details.

Here is some material that may be useful to you.

[jobbie]

Please provide some details.

Here is some material that may be useful to you.

thanks for the reply. Let me explain a little better. I created a db and saved it in folder say "A". I then created a form which was linked to Table "T". The form was in datasheet view. I then created an accde and saved it on the desktop. I then deleted/updated some rows from the form in the accde. So I assume the updation should also happen in the table "T" of the original db saved in folder "A". Am I right? But when I open the table T in the original db I don't see the updated rows.

[jobbie]

My question is if I need to replace the accde on the desktop do I have to create a new accde from the source and replace the one on the desktop? And if by doing so will there be any changes made to the tables or the queries?

[HiTechCoach]

I then created a form which was linked to Table "T".

When you say linked to Table "T" does that mean the table in a linked table that is in a back end database?

For this to work yiu must have a split database. Is that what you have?


My suspicion is that the Table T is a local table in the accde file. Is this is true then the data is not shared.


I have written some article on the subject: Split Database (Click Here)

[jobbie]

When you say linked to Table "T" does that mean the table in a linked table that is in a back end database?

For this to work yiu must have a split database. Is that what you have?


My suspicion is that the Table T is a local table in the accde file. Is this is true then the data is not shared.


I have written some article on the subject: Split Database (Click Here)

no the db has not been split. Only an accde was created from the source. Now I would like to modify some of the forms in the db but I am afraid if I were to create a new accde and overwrite the existing accde it would overwrite all my tables and queries.

[HiTechCoach]

no the db has not been split. Only an accde was created from the source. Now I would like to modify some of the forms in the db but I am afraid if I were to create a new accde and overwrite the existing accde it would overwrite all my tables and queries.

That is correct.

You need to first split the database into a application (front end) and Data (back end - Tables). The application (front end) is what you compile into a .accde.

By splitting your database into an application (front end) and data (back end) you can replace the application (front end) with without over writing any of the tables since they are in the back end.

If you do not split the database you have to import all the tables from the old accde into the new accde. Lot of work and lots of room for error.

[jobbie]

That is correct.

You need to first split the database into a application (front end) and Data (back end - Tables). The application (front end) is what you compile into a .accde.

By splitting your database into an application (front end) and data (back end) you can replace the application (front end) with without over writing any of the tables since they are in the back end.

If you do not split the database you have to import all the tables from the old accde into the new accde. Lot of work and lots of room for error.

So what is the solution now that I have already created an accde without splitting?

[orange]

Typically you would not create an accde until the very end of development and testing.
The steps are conceptual design, development, split database, test, review, accept for "production",
--then -- make a backup of your FE and BE. Create an accde from your FE for distribution.

Your backup of the FE from which you create the accde is absolutely necessary. Guard it as gold. You must work with the accdb version when you modify anything in your front end. After you have made modifications to the FE (accdb), BACK IT UP!, then make an accde from a copy.

Bottom line --you can not adjust/modify an accde -- you modify the accdb from which the accde was made. Also, if you are running a MsAccess db with more than 1 user, you split your database.

Good luck.

see this for more split info

[jobbie]

Typically you would not create an accde until the very end of development and testing.
The steps are conceptual design, development, split database, test, review, accept for "production",
--then -- make a backup of your FE and BE. Create an accde from your FE for distribution.

Your backup of the FE from which you create the accde is absolutely necessary. Guard it as gold. You must work with the accdb version when you modify anything in your front end. After you have made modifications to the FE (accdb), BACK IT UP!, then make an accde from a copy.

Bottom line --you can not adjust/modify an accde -- you modify the accdb from which the accde was made. Also, if you are running a MsAccess db with more than 1 user, you split your database.

Good luck.

see this for more split info

thanks for the valuable advice but what do you suggest I do now? Should I import all the tables from my accde into the source and then recreate a new accde?

[orange]

How about stepping back and telling us about:

-your database (how many tables, how many users, ...) (size and importance)
-your specifications/documentation (project overview, design documents, testing, user manual...)(formality)
-your background (seems accdb/accde/split are all new terms/concepts) (experience)

Getting your database tables designed to meet your business needs is a key step in building an application. Splitting your database for various reasons is also important.

Is this something you built for yourself, or was this a formal project requested by management?

What is you main concern at this time?

[jobbie]

-your database there are many tables but I am sure only 1 of them has been modified via the accde

-your specifications/documentation it's not a professional application, just something I built myself and I am the only user but I use it at work and we are very dependent on it.

-your background I am a novice. I know what accde and split is but not sure of accdb

What is you main concern at this time? I would like to split the db and start again but there are many records which have already been modified via the accde and the source does not reflect them. So splitting and creating a new accde may lead to problems.

[orange]

It is difficult to understand your situation.
I don't understand

there are many records which have already been modified via the accde and the source does not reflect them.

and

I am the only user but I use it at work and we are very dependent on it.

It appears that the risk/vulnerability associated with the use of a non split database in a work environment is only going to increase as time goes on. You correct the design now or later. But you need to have a plan and some experience.

[ItsMe]

...Should I import all the tables from my accde into the source and then recreate a new accde?

I would import the tables into a new blank database and treat that as the backend. If you have a copy of the accdb that you used to create the accde, use a copy of that to link to your new backend. With this new accdb frontend, create an accde and provide it to the User. Your new accdb can be edited and then used to create new versions of the accde.

I use special folders to store copies that are archived, master accde, accdb used for revisions, etc.

[HiTechCoach]

I would import the tables into a new blank database and treat that as the backend. If you have a copy of the accdb that you used to create the accde, use a copy of that to link to your new backend. With this new accdb frontend, create an accde and provide it to the User. Your new accdb can be edited and then used to create new versions of the accde.

Ditto! That is exactly how I split database all the time.