ABOUT compiling loadable modules

First off I am an ameteur and a rookie. I am might attempt to "compile" a
database soon, or in otherwords, create a run time, resaleable module. A few
questions:

1) If I use splitter, and create a front end and back end, can I compile to
include both the back and front end? Or do I compile them separately and one
knows how to look for the other via file names and extensions, example:
frontend.exe looks for backend.dll

2) As I come up with "updates" to my "front end", can I just "recompile" the
frontend and then just copy or port it over to the laptop that is running the
system, as in my example above I would just replace
frontend.dll.............or do I have to "recompile" the backend and frontend
into a new single loadable module?

3) any tips and other things to watch out for, with "compiling", in general?

To distribute "strand-alone" applications you need to have the developer
extensions for Access 2003 or developer version of access for previous
versions, those versions will create a package that you can distribute and
will allow you to have a backend-frontend format,

Those developer tools won't create an .exe or .dll, but they will distribute
a royalty-free runtime utility with your packaged application,

For more details:

http://msdn.microsoft.com/office/tec...s/default.aspx
--
jl5000
a href="http://www.joshdev.com"/a


"mark r" wrote:

First off I am an ameteur and a rookie. I am might attempt to "compile" a
database soon, or in otherwords, create a run time, resaleable module. A few
questions:

1) If I use splitter, and create a front end and back end, can I compile to
include both the back and front end? Or do I compile them separately and one
knows how to look for the other via file names and extensions, example:
frontend.exe looks for backend.dll

2) As I come up with "updates" to my "front end", can I just "recompile" the
frontend and then just copy or port it over to the laptop that is running the
system, as in my example above I would just replace
frontend.dll.............or do I have to "recompile" the backend and frontend
into a new single loadable module?

3) any tips and other things to watch out for, with "compiling", in general?

You didn't answer my questions, if you care, re-read the questions and
provide an answer..thanks anyway

"jl5000" wrote:

To distribute "strand-alone" applications you need to have the developer
extensions for Access 2003 or developer version of access for previous
versions, those versions will create a package that you can distribute and
will allow you to have a backend-frontend format,

Those developer tools won't create an .exe or .dll, but they will distribute
a royalty-free runtime utility with your packaged application,

For more details:

http://msdn.microsoft.com/office/tec...s/default.aspx
--
jl5000
a href="http://www.joshdev.com"/a


"mark r" wrote:

First off I am an ameteur and a rookie. I am might attempt to "compile" a
database soon, or in otherwords, create a run time, resaleable module. A few
questions:

1) If I use splitter, and create a front end and back end, can I compile to
include both the back and front end? Or do I compile them separately and one
knows how to look for the other via file names and extensions, example:
frontend.exe looks for backend.dll

2) As I come up with "updates" to my "front end", can I just "recompile" the
frontend and then just copy or port it over to the laptop that is running the
system, as in my example above I would just replace
frontend.dll.............or do I have to "recompile" the backend and frontend
into a new single loadable module?

3) any tips and other things to watch out for, with "compiling", in general?

Actually, he did answer your questions indirectly.

You appear to be under the misconception that compiling an access
application changes it into an executable. In Access, compiling simply looks
at all of the code and ensures that there are no compile-time errors (as
opposed to run-time errors)

There is no way to convert an Access application into an executable. If your
intent is to distribute your application to users who don't already have
Access installed, your option is, as jl5000 wrote, to use "the developer
extensions for Access 2003 or developer version of access for previous
versions." This allows you to package your application together with a
royalty-free run-time version of Access. Users who don't already have Access
installed can install the run-time, and will then be able to use your
application. They will not be able to make design changes to it, though.
Note that packaging your application together with the run-time does not
change your application in any way, shape or form. (Note, too, that run-time
applications have to be designed a little differently than non-run-time
applications. It's important that you have rigorous error trapping, plus you
need to ensure that there's at least a start up form defined)

You need to put code in your front-end to ensure that your users can find
the back-end if your front-end is pointing to the correct location. A sample
of code that you can use is http://www.mvps.org/access/tables/tbl0009.htm at
"The Access Web"

When your front-end changes, you simply give the users a new version of your
front-end. Nothing further should be required.


--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"mark r" wrote in message
...
You didn't answer my questions, if you care, re-read the questions and
provide an answer..thanks anyway

"jl5000" wrote:

To distribute "strand-alone" applications you need to have the developer
extensions for Access 2003 or developer version of access for previous
versions, those versions will create a package that you can distribute
and
will allow you to have a backend-frontend format,

Those developer tools won't create an .exe or .dll, but they will
distribute
a royalty-free runtime utility with your packaged application,

For more details:

http://msdn.microsoft.com/office/tec...s/default.aspx
--
jl5000
a href="http://www.joshdev.com"/a


"mark r" wrote:

First off I am an ameteur and a rookie. I am might attempt to "compile"
a
database soon, or in otherwords, create a run time, resaleable module.
A few
questions:

1) If I use splitter, and create a front end and back end, can I
compile to
include both the back and front end? Or do I compile them separately
and one
knows how to look for the other via file names and extensions, example:
frontend.exe looks for backend.dll

2) As I come up with "updates" to my "front end", can I just
"recompile" the
frontend and then just copy or port it over to the laptop that is
running the
system, as in my example above I would just replace
frontend.dll.............or do I have to "recompile" the backend and
frontend
into a new single loadable module?

3) any tips and other things to watch out for, with "compiling", in
general?