saveas in access

[philfer]

Hello

Is there a saveas for a database in access

I am creating a reporting database that will use new data each month and thus i want to open the previous months database get the new date and then save the database as a new version with a new name

There is a saveas in the office button menu does anyone know if there is a way to do it in vba

Thanks
Phil

 

[HiTechCoach]

Hello

Is there a saveas for a database in access

I am creating a reporting database that will use new data each month and thus i want to open the previous months database get the new date and then save the database as a new version with a new name

There is a saveas in the office button menu does anyone know if there is a way to do it in vba

Thanks
Phil

Phil,


I would urge you too split your database into a front end and back end if not already.

I would recommend two other methods:

1) design your tables ot have a field for the period. Import your new data into the same table. You can use the field to select the desired records. This will allow you to easily get stats across periods.

or

2) copy a blank back end to a new name and relink to this new back end. This way you have only one front end that you have to maintain.


Hope this helps ...

 

[philfer]

Hi boyd

Thanks for your reply

The database is quite small and i am so far down the line i dont really want to start making big structural changes.

If i create a blank back end i would still have to copy all the tables and relationships to it. Also having only one front end and many back ends would cause complications when changing the view date of reports i.e. i would have to reconnect to a previous backend

For an unsophisticated app such as mine it would be so easy just to be able to save it as a new filename. I have tried runcommand, copydatabasefile and even filesystemobject but cant seem to crack this one

Its a real doozy!!!

Thanks again and if you have any further thoughts i would receive them gladly

Cheers
Phil

 

[boblarson]

And just to add - copying an access database for each period is a sure fire way to get your IT department furious with you. They usually hate to see Access databases anyway but to see them multiply and multiply is one that really grinds their gears.

 

[philfer]

Why do IT departments hate access databases so much ?

cheers
phil

 

[boblarson]

Why do IT departments hate access databases so much ?

cheers
phil

Well, one reason is that normally users do not design them properly to begin with. They do things like copy a new one for each month instead of creating the structure so it is sound and is a SINGLE database that gets used over and over. So they multiply like rabbits.

The other thing is that many users just do not know how to design things well and then a database is designed like that and people come to depend on it and then the person who designed and programmed it leaves and guess who is stuck supporting it? Yep, the IT department.

 

[HiTechCoach]

Hi boyd

Thanks for your reply

The database is quite small and i am so far down the line i dont really want to start making big structural changes.

I do not see this being any kind of big structural change to allow all periods to be in a single database. It usually only requires adding a a single field so a few tables.

Nothing major!

If i create a blank back end i would still have to copy all the tables and relationships to it.

Not really. That was not what I was suggestion. By blank, I was referring to the data. All the tables and relationships, look up table data, etc would be there.

Also having only one front end and many back ends would cause complications when changing the view date of reports i.e. i would have to reconnect to a previous backend

If that is a problem, Even more reason to have a single back end.

For an unsophisticated app such as mine it would be so easy just to be able to save it as a new filename.

Why not just copy a database with all the objects by no data!

I have tried runcommand, copydatabasefile and even filesystemobject but cant seem to crack this one

Its a real doozy!!!

Another good reason to use a single back end and import all data into one databases.

IMHO, I believe all your difficulties are coming from having multiple databases. They are are only complicating matters for you

I sure would not want to have to maintain all those databases caused by creating a new database every month. <shuddering at the thought>