What do we need to make our solutions into standalones?

[StargateFan]

Thanks.

 

[John Vinson]

Thanks.

You'll have to explain what your solution is, and what you consider a
standalone.

If you're asking "how can I compile my Access .mdb file into an
executable" - you can't.


John W. Vinson[MVP]

 

[Douglas J Steele]

As John's already told you, you cannot convert an Access application into an
executable.

What you can do, though, is package your application together with a
royal-free runtime version of Access. Your users will be able to install the
runtime version if they don't already have Access installed, and then will
be able to use your application (but not make design changes to it).

See what Tony Toews has at
http://www.granite.ab.ca/access/developereditionfaq.htm for more details.

 

[StargateFan]

As John's already told you, you cannot convert an Access application into an
executable.
[snip]

What you can do, though, is package your application together with a
royal-free runtime version of Access. Your users will be able to install the
runtime version if they don't already have Access installed, and then will
be able to use your application (but not make design changes to it).

That's exactly what I meant. Sorry. FMP users would have known what
I meant as that's where I learned terminology <lol>. I assumed it was

See what Tony Toews has at
http://www.granite.ab.ca/access/developereditionfaq.htm for more details.

Super, will check this out.

 

[chakatheapeman]

This is a tricky purchase.

It is part of the Office development toolkit. Last year when I purchased it, I was required to by MSDN universal, $2,500 or so. I didn’t mind so much because I needed the other licenses anyway. However, it was unclear that you get the office toolkit with Pro but not the packager. That was only in Universal

In previous years this was sold differently. The MSDN structure has also changed. I would call MSDN subscriptions and get a strait answer on this. I bought pro and then had to cancel on get universal. That was a long complicated change. It took me a day just to find out that the packager only ships with universal.

Also, read up on the runtime addition. Errors are not displayed to the user and stuff. No support for those goofy data access pages either.