Update front end of database using Developer Package Solution

[james]

AAAAA

Doug, thank you so much for your quick response.

I did see your reply to someone else with this suggestion (which is a very
good suggestion). However, I need a medium to have an "install package"
for
remote users; one that they can click on to have it automatically install
the
updated front end. I thought that by using the developer's package
solution, which creates a setup exec, it would do it for me. Make sense?

 

[james]

SO

Yes, you need to package the application with the runtime so that those
users who don't already have Access installed will be able to use your
application. However, once they've installed the runtime, there's no
reason to make them download the entire package again.

All that's required is to replace the front-end.

 

[Karan]

I have a split database, and it will be used on multiple PCs (not a server).
I used the developer "package solution" to provide the front and back end
databases to the users. I then updated a form on the front end database and
used the developer "package solution" again to provide to the users an update
of just the front end. When executed on a remote PC, it did not update the
front end database. What am I doing wrong?

Any help you can provide would be much appreciated!

 

[Douglas J. Steele]

Try simply replacing the mdb (or mde or accdb or accde or whatever format
your front-end is in), rather than redistributing a repackaged solution.

 

[Karan]

Doug, thank you so much for your quick response.

I did see your reply to someone else with this suggestion (which is a very
good suggestion). However, I need a medium to have an "install package" for
remote users; one that they can click on to have it automatically install the
updated front end. I thought that by using the developer's package
solution, which creates a setup exec, it would do it for me. Make sense?

 

[Douglas J. Steele]

Yes, you need to package the application with the runtime so that those
users who don't already have Access installed will be able to use your
application. However, once they've installed the runtime, there's no reason
to make them download the entire package again.

All that's required is to replace the front-end.

 

[hor vannara]

I have a split database, and it will be used on multiple PCs (not a
server).
I used the developer "package solution" to provide the front and back end
databases to the users. I then updated a form on the front end database
and
used the developer "package solution" again to provide to the users an
update
of just the front end. When executed on a remote PC, it did not update
the
front end database. What am I doing wrong?

Any help you can provide would be much appreciated!