Question about Access coding practice/process...

  • Thread starter Thread starter ohaya
  • Start date Start date
O

ohaya

Hi,

I'm very new to Access coding, so pardon me if this is a dumb question...

When you implement forms with coding, the code for the forms and modules are
embedded in the Access MDB file, i.e., the code and the database tables
themselves are "integrated".

Since this is the case, I was wondering what you all do when you have
changed the code/processing, and want to move this new code to an existing
database/MDB file without disturbing the database itself?

For example, I'm developing an Access application. I've been sending the
MDB files to my customer for them to review and test.

At some point, they'll be putting real data into their database (using my
app), but I'll probably be continuing to revise the code for a bit.

How do I get the code changes into the MDB that they have?

Thanks,
Jim
 
Hi Jim,

This is when you split the database creating a frontend mdb (forms, queries,
modules, reports) and a backend mdb (tables only). The production backend
stays in place while you can swap the front-ends very easily.

Splitting is very easy, simply use the wizard (Tools->Database
Utilities->Database Splitter). This will move the tables into their own mdb
and create linked tables in the frontend. For most things, the splitting is
transparent.

There are a few things to watch - if you use DAO and use tabletype
recordsets you'll have to modify your code a bit.

You'll need to become aquainted with the "Linked Table Manager"
(Tools->Database Utilities->Linked Table Manager). After the initial split,
if you move the backend mdb, you have to tell the frontend where the data is
located - this wizard helps you do that. It works and suffices but is slow
and not intuitive so eventually, you may want to adapt your own table
relinking code - fortunatley it's already written and can be found here:
http://www.mvps.org/access/tables/tbl0009.htm.

Some other things to watch for are described here:

http://www.granite.ab.ca/access/performancefaq.htm
 
Sandra,

Wow, that was quick. I don't think that I could've even typed your answer,
much less made it, that fast :).

Ok, thanks, I'll give what you suggested a try...

Jim



Sandra Daigle said:
Hi Jim,

This is when you split the database creating a frontend mdb (forms, queries,
modules, reports) and a backend mdb (tables only). The production backend
stays in place while you can swap the front-ends very easily.

Splitting is very easy, simply use the wizard (Tools->Database
Utilities->Database Splitter). This will move the tables into their own mdb
and create linked tables in the frontend. For most things, the splitting is
transparent.

There are a few things to watch - if you use DAO and use tabletype
recordsets you'll have to modify your code a bit.

You'll need to become aquainted with the "Linked Table Manager"
(Tools->Database Utilities->Linked Table Manager). After the initial split,
if you move the backend mdb, you have to tell the frontend where the data is
located - this wizard helps you do that. It works and suffices but is slow
and not intuitive so eventually, you may want to adapt your own table
relinking code - fortunatley it's already written and can be found here:
http://www.mvps.org/access/tables/tbl0009.htm.

Some other things to watch for are described here:

http://www.granite.ab.ca/access/performancefaq.htm

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.
Hi,

I'm very new to Access coding, so pardon me if this is a dumb question...

When you implement forms with coding, the code for the forms and modules
are embedded in the Access MDB file, i.e., the code and the database
tables themselves are "integrated".

Since this is the case, I was wondering what you all do when you have
changed the code/processing, and want to move this new code to an existing
database/MDB file without disturbing the database itself?

For example, I'm developing an Access application. I've been sending the
MDB files to my customer for them to review and test.

At some point, they'll be putting real data into their database (using my
app), but I'll probably be continuing to revise the code for a bit.

How do I get the code changes into the MDB that they have?

Thanks,
Jim
Click to expand...
Click to expand...
 
You're welcome :-)

Post back if you have more questions or run into other issues

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.
Sandra,

Wow, that was quick. I don't think that I could've even typed your
answer, much less made it, that fast :).

Ok, thanks, I'll give what you suggested a try...

Jim



Sandra Daigle said:
Hi Jim,

This is when you split the database creating a frontend mdb (forms,
queries, modules, reports) and a backend mdb (tables only). The
production backend stays in place while you can swap the front-ends very
easily.

Splitting is very easy, simply use the wizard (Tools->Database
Utilities->Database Splitter). This will move the tables into their own
mdb and create linked tables in the frontend. For most things, the
splitting is transparent.

There are a few things to watch - if you use DAO and use tabletype
recordsets you'll have to modify your code a bit.

You'll need to become aquainted with the "Linked Table Manager"
(Tools->Database Utilities->Linked Table Manager). After the initial
split, if you move the backend mdb, you have to tell the frontend where
the data is located - this wizard helps you do that. It works and
suffices but is slow and not intuitive so eventually, you may want to
adapt your own table relinking code - fortunatley it's already written
and can be found here: http://www.mvps.org/access/tables/tbl0009.htm.

Some other things to watch for are described here:

http://www.granite.ab.ca/access/performancefaq.htm

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.
Hi,

I'm very new to Access coding, so pardon me if this is a dumb
question...

When you implement forms with coding, the code for the forms and modules
are embedded in the Access MDB file, i.e., the code and the database
tables themselves are "integrated".

Since this is the case, I was wondering what you all do when you have
changed the code/processing, and want to move this new code to an
existing database/MDB file without disturbing the database itself?

For example, I'm developing an Access application. I've been sending
the MDB files to my customer for them to review and test.

At some point, they'll be putting real data into their database (using
my app), but I'll probably be continuing to revise the code for a bit.

How do I get the code changes into the MDB that they have?

Thanks,
Jim
Click to expand...
Click to expand...
Click to expand...
 
Back
Top