Development at different geographic sites

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I would like to check out a form or a table and send it by email or FTP to the other developer. Let him work on it and email back the result to check in the updated form or table. I will keep the master. We will both work on different parts of the application
 
tonyaims said:
I would like to check out a form or a table and send it by email or
FTP to the other developer. Let him work on it and email back the
result to check in the updated form or table. I will keep the master.
We will both work on different parts of the application
Click to expand...

Just create a blank db and have it open at the same time as your master.
Drag the object you want to migrate into the blank db. Alternatively you can
export the object to the blank db.
Send the "no longer blank" (but probably totally inoperable) db to you mate.
He can import/export into his copy (or a copy of his copy) and away you go.
 
Damian - I copied 2 tables and a form with a subform into the new .mdb file. Everything was OK except that when I opened the form, I got an error message that the table for the subform could not be found.
 
tonyaims said:
Damian - I copied 2 tables and a form with a subform into the new
.mdb file. Everything was OK except that when I opened the form, I
got an error message that the table for the subform could not be
found.
Is there something else that needs to be done to capture everything
that Access wants regarding subforms? Is there another way to share
forms with subforms?
Click to expand...

The structure of the data side of the database (tables, relationships and
queries) has to be exactly the same as the database in which the other
objects were created. You'll probably need to create relationships in the
"Import" database before the dependant forms / reports / queries will work.
I use this "export" method myself with my current project but I seldom
change the structure of the database, usually it's only new forms and
reports. I keep a copy on my local machine where I develop the objects, then
when no users are connected to the "production version" (on the WAN), I
upload the new objects. From time to time I delete the development version
and copy over a fresh copy of the production version.
I think in this case your answer lies in the relationships. As far as I know
there's no way to export the relationship definitions (but I would be
interested to see the reaction of an Access guru to this).

cheers

Damien
 
Back
Top