Form and reports design get modified when imported to a another database

[Emmanuel]

I have a database which I frequently add more features to it.



But whenever I want to do a major update, I usually prefer doing it on a new access database so that when I get the desired results, I can finally import into my main database.

But I have noticed recently that, when ever I import the new database to my main database, the form and report design changes.
By that I mean, colours, font sizes and a times some of the arrangements of some fields are affected.

So I end up doing another whole designing again except for the codes which remains the same

Is there something am not doin right?

How do I fix this?

[isladogs]

Probably related to themes. Make sure your old and new versions use exactly the same theme...

But you are making extra work for yourself with this approach.
Why not just do development work in a copy of your database so there is no need to import updated objects back again....

[Emmanuel]

Probably related to themes. Make sure your old and new versions use exactly the same theme...

But you are making extra work for yourself with this approach.
Why not just do development work in a copy of your database so there is no need to import updated objects back again....

The main work has so many objects so I didn’t want a situation where I might mistakenly delete an object or modify an object am not supposed to touch.

And I about the theme, I use access default themes for all my reports and forms

[Welshgasman]

So working on a copy, it would not matter if you were careless or not?

[Emmanuel]

So working on a copy, it would not matter if you were careless or not?

How do u mean buddy?

[Welshgasman]

How do u mean buddy?

Well if you work on a copy

mistakenly delete an object or modify an object am not supposed to touch.

will not matter as it is a copy?

You could try just copying the structure as your test DB (if you continue that method) and then copy your objects to that, amend and copy back.?
See if that makes any difference?

I must admit, I used to make a backup of my FE, then amend the original. If I made such a huge mistake, then I just would go back to my backup?
I could backup at the touch of a button, so I could have a good few backups just through one day

[isladogs]

If you really want to continue with your approach rather than working on a copy then you need to make sure that the theme used in your database is saved as your default theme.
Then when you create a new database it will automatically use that theme and you should no longer have the issues you describe

[Emmanuel]

If you really want to continue with your approach rather than working on a copy then you need to make sure that the theme used in your database is saved as your default theme.
Then when you create a new database it will automatically use that theme and you should no longer have the issues you describe

How do I make it my default theme?
Because I will like to use this approach for major updates on the database

[Emmanuel]

If you really want to continue with your approach rather than working on a copy then you need to make sure that the theme used in your database is saved as your default theme.
Then when you create a new database it will automatically use that theme and you should no longer have the issues you describe

You were right about the themes. I noticed the new database was created with a different theme and that was the cause of the issue.

Looking forward, I will have to export my theme and apply it to any new test db I will be working on.

Thanks so much for your time.

[isladogs]

There care several ways of saving the default theme.
The simplest is probably to open a form which has the theme settings required in design view.
Now open the Form Design ribbon ...Themes dropdown ...Save Current Theme ...and give it a suitable name



Close and open a new database. It should retain that theme.
If not go to Access options, Client Settings, scroll to the bottom and select your default theme

If even that fails, I have another two solutions... but it shouldn't be necessary!