OK but the program is not a centralized program each school has thier own
copy of it adn I want to get away from having to create the users version
every year for them.
"Marshall Barton" <(E-Mail Removed)> wrote in message
news

(E-Mail Removed)...
> Dorian Chalom wrote:
>
> >But I have modules too to copy over. So I guess I could create this code
in
> >a seperate module and in the module part of the transfer over filter out
> >this module with an IF...ENDIF so it would not copy this opwen module.
> >
> >Yes????
>
> Maybe, if you make certain that all copied objects are
> closed first. The CopyObject method is probably more
> appropriate than TransferDatabase
>
> It sounds as if you're trying to write code to update the
> user's copy of your application to include your new
> forms/reports/code. If so, this is not a good way to go
> about it. It is **MUCH** better to copy a complete new
> front end MDB file to each user's machine. See Tony Toews'
> thoughts on this question:
>
> http://www.granite.ab.ca/access/splitapp.htm
> and
> http://www.granite.ab.ca/access/autofe.htm
>
> --
> Marsh
> MVP [MS Access]