Creating executable version in msAccess

[Guest]

Hi all,

1) How do I create a exe in msAccess ?
2) If I want to use msaccess as front end to sql server how do I go about it
(ie, I have created web pages linking it to sql server database) but ?

Create a blank database -> go to Web pages - > create Web pages - > then how
do I create exe ?

Will the connection properties be stored in exe created ? When I use the exe
on different machines will then exe still be good (ie, will get connected to
sql server) ?

Thanks
Madhuri

 

[John Vinson]

Hi all,

1) How do I create a exe in msAccess ?

You cannot. The option is not available.


John W. Vinson[MVP]

 

[Guest]

Now I know how to create a web page without opening the access database and
have created a web page with sql server database connection and I ve
successfully opened it in IE. Now I want to know how to bind different web
pages together like in a menu and distribute it among users .I need to know
whether there is any concept of creating a executable version in msaccess
like we do with other front ends ?

Thanks
Madhuri

 

[Mike Labosh]

1) How do I create a exe in msAccess ?

You don't. It mystifies me that this rumor continues to go around. For
whatever reason you want an exe program, the next closest three things you
can do are:

1. "compile" it to a .mde file (The user will still have to have MS Access)
2. Purchase the "Access Developer's Toolkit" (I think it's still called
that) and distribute your application with the Runtime Edition of Access
(The user will NOT have to have MS Access)
3. Migrate your application from Access to something like VB 6.0 or VB.NET.
(User will not need anything but what you give them)

2) If I want to use msaccess as front end to sql server how do I go about
it
(ie, I have created web pages linking it to sql server database) but ?

I personally am a bit weak on that one, because when I talk to SQL Server, I
use VS.NET. In Access, you want to make a .adp file ("Access Database
Project") and point it at your SQL Server. Here's a sample one to get you
started (path may differ with your version):

C:\Program Files\Microsoft Office\OFFICE11\SAMPLES\NorthwindCS.adp

When you open this in Access, you will have to click File -> Connection and
point to a Northwind database in a SQL Server.

Create a blank database -> go to Web pages - > create Web pages - > then
how
do I create exe ?

Like I mentioned, sadly, you cannot. If you are actually looking to have a
web application against a SQL database, the proper thing would be to use
Visual InterDev 6.0 or Visual Studio.NET. Using Access as a middle man,
even though it's so super easy to use, is very poor design. BTW -- don't
even THINK of using FrontPage for this

Will the connection properties be stored in exe created ? When I use the
exe
on different machines will then exe still be good (ie, will get connected
to
sql server) ?

If you make a .adp with Access, I believe the connection stuff is stored in
the .adp file, and therefore will be portable among users.

Also, similar to how you can "compile" an mdb to an mde, you can compile an
adp to an ade. But even if you do so, if you give a user an adp or ade,
they will still have to have Access.

--
Peace & happy computing,

Mike Labosh, MCSD
"Working here is like living inside a Salvador Dali painting." -- Me. Yeah,
ME! [Oh fer cryin out loud]

 

[Mike Labosh]

Now I know how to create a web page without opening the access database

and
have created a web page with sql server database connection and I ve
successfully opened it in IE. Now I want to know how to bind different web
pages together like in a menu and distribute it among users .I need to
know
whether there is any concept of creating a executable version in msaccess
like we do with other front ends ?

Here is another whammy.

Any Web Pages you create in Access as a "Data Access Page" require special
ActiveX controls to download to the user that's viewing your page. These
special ActiveX controls are NOT freely distributable. The user is required
to have Access, or a valid runtime license purchased from Microsoft in order
to view your Data Access Page.

--
Peace & happy computing,

Mike Labosh, MCSD
"Working here is like living inside a Salvador Dali painting." -- Me. Yeah,
ME! [Oh fer cryin out loud]

 

[Guest]

Thank you Mike and John

Your explanation was useful.

Madhuri

Now I know how to create a web page without opening the access database
and
have created a web page with sql server database connection and I ve
successfully opened it in IE. Now I want to know how to bind different web
pages together like in a menu and distribute it among users .I need to
know
whether there is any concept of creating a executable version in msaccess
like we do with other front ends ?

Here is another whammy.

Any Web Pages you create in Access as a "Data Access Page" require special
ActiveX controls to download to the user that's viewing your page. These
special ActiveX controls are NOT freely distributable. The user is required
to have Access, or a valid runtime license purchased from Microsoft in order
to view your Data Access Page.

--
Peace & happy computing,

Mike Labosh, MCSD
"Working here is like living inside a Salvador Dali painting." -- Me. Yeah,
ME! [Oh fer cryin out loud]

 

[Larry Linson]

Here is another whammy.

Any Web Pages you create in Access as a "Data Access Page" require special
ActiveX controls to download to the user that's viewing your page. These
special ActiveX controls are NOT freely distributable. The user is
required to have Access, or a valid runtime license purchased from
Microsoft in order to view your Data Access Page.

I believe with Access 2003 Data Access Pages, the Office Web Extensions are
freely downloadable from Microsoft and no longer require the user have
Access installed.

 

[Douglas J. Steele]

2. Purchase the "Access Developer's Toolkit" (I think it's still called
that) and distribute your application with the Runtime Edition of Access

It's not still called that. You need to purchase the following in order to
create an Access 2003 runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.

If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

 

[Mike Labosh]

I believe with Access 2003 Data Access Pages, the Office Web Extensions

are freely downloadable from Microsoft and no longer require the user have
Access installed.

Not the Office Web Extensions. I'm talking about the bizzare remote data
access controls that directly access the data from the front-side browser.
--
Peace & happy computing,

Mike Labosh, MCSD
"Working here is like living inside a Salvador Dali painting." -- Me. Yeah,
ME! [Oh fer cryin out loud]

 

[Mike Labosh]

It's not still called that. You need to purchase the following in order to

create an Access 2003 runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003
runtime components and you have to have Access 2003 installed in order to
install the ADE.

If you're using MSDN, note that while VSTO is available in all
subscription levels of MSDN, the Access Developer Extensions are not
included with all versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

Excellent clarification!

--
Peace & happy computing,

Mike Labosh, MCSD
"Working here is like living inside a Salvador Dali painting." -- Me. Yeah,
ME! [Oh fer cryin out loud]

 

[Guest]

I realize this is more than a year late, but I can't believe none of the guys
on this board back then suggested you save your Access database as a Access
Project (.adp). It allows very much flexibility, and if you use the MSDE
instead of SQL Server, there's no real additional cost or big learning curve.

Essentially, with a very few exceptions, your .adp will behave just as it
does as an .mdb, but since it connects to an outside source for it's data
(such as SQL Server or MSDE) you don't have single-user issues to deal with,
etc., etc., etc...

....I should also say that this is mostly deprecated information to those
folks already developing with A2007, as it seems to me new and improved with
respects to publishing form-based web pages to the internet...but works great
for me ;-)