releasing new code

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Christopher Glaeser - 30 Mar 2005 22:16 GMT

After you have developed and tested a new set of features in a copy of a
database, what is your solution for migrating those changes from the copy to
the released database? I can have single-user access to the database after
normal business hours, so the changes do not have to occur while others are
tyring to use the database. I can purchase third-party tools if needed.
Access 2003 and Windows XP.

Best,
Christopher

Reply to this Message

John Webb - 30 Mar 2005 22:53 GMT

Personally, whenever I have worked on database for multiple users, I split
the database into a back end and front end. Then when I update the front
end I simply redistribute this to my users.

If the back end needs updating I tend to do one of two things:

1. If the changes are minor, I tend to make all users aware of a "system
outage", then copy the existing data from the old back end into my new one,
and then replace it.

2. If the changes are major, i.e adding a whole new area of functionality,
I have been known to create an entirely separate back end for this, and
link to both from the front end.

Option 1 is my usual choice, option 2 has only become necassary twice so
far - the most recent was when I updated a HR database to include Fleet
Management info - I simply created a separate back end for this.

Cheers

John Webb

Reply to this Message

Christopher Glaeser - 31 Mar 2005 00:27 GMT

> Personally, whenever I have worked on database for multiple users, I split
> the database into a back end and front end. Then when I update the front
> end I simply redistribute this to my users.

OK, sounds easy enough.

> If the back end needs updating I tend to do one of two things:
>
> 1. If the changes are minor, I tend to make all users aware of a "system
> outage", then copy the existing data from the old back end into my new
> one,
> and then replace it.

I can get single-user access to the database during off hours, so that
should be doable. Once the database is split and I am working on a copy of
the FE/BE, will I be able to add/edit tables and relationships just as I do
now with a single MDB file?

Best,
Christopher

Reply to this Message

PC Datasheet - 31 Mar 2005 01:13 GMT

Yes, you will be able to add/edit tables and relationships just as you do
now with a single MDB file. The only thing to remember is that if you add
new tables, you must link to them from the front end. Once a link is
established, editing tables and relationships is automatically taken care of
through the link.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
resource@pcdatasheet.com
www.pcdatasheet.com

> > Personally, whenever I have worked on database for multiple users, I split
> > the database into a back end and front end. Then when I update the front
[quoted text clipped - 16 lines]
> Best,
> Christopher

Reply to this Message

Graham Mandeno - 30 Mar 2005 22:58 GMT

Hi Christopher

Split the database into front-end and back-end. Then you can just replace
the entire front-end. See here for details:
http://www.granite.ab.ca/access/splitapp/index.htm

Signature

Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

> After you have developed and tested a new set of features in a copy of a
> database, what is your solution for migrating those changes from the copy
[quoted text clipped - 5 lines]
> Best,
> Christopher

Reply to this Message