splitting of Access database

[Nandini]

Hi everybody,

I have created one mdb file using MS Access 2003. After splitting this, the
back end of this file is migrated into sql server (Express 2005) using SSMA
for Access. The front end containing tables and forms are in mdb file.
Is it possible to create an exe file on the basis of this? If it is possible
please let me know how it can be done. Earliest response will be highly
appreciated.

With regards

 

[John W. Vinson]

Hi everybody,

I have created one mdb file using MS Access 2003. After splitting this, the
back end of this file is migrated into sql server (Express 2005) using SSMA
for Access. The front end containing tables and forms are in mdb file.
Is it possible to create an exe file on the basis of this? If it is possible
please let me know how it can be done. Earliest response will be highly
appreciated.

With regards

No, it is not possible.

An Access database is not an .exe file and cannot, in any way, be made into an
..exe file.

You must have some version of Access - the retail program or the Runtime - in
order to use the Access frontend. The .mdb file can be compiled into a .mde
file, but this just removes the source code and prevents the user from going
into design view.

If you want an .exe file frontend then you must rebuild it from scratch in
Visual Studio or some other appropriate program.

 

[Jack Leach]

The front end containing tables and forms

In a split database, the backend is supposed to contain tables, and the
frontend is supposed to contain queries.

Is it possible to create an exe file on the basis of this?

Not exactly, but you can create an MDE of the frontend rather than an EXE.
An MDE file is an executable in a sense (instead of Microsft Data Base file,
you have a Microsoft Data Executable? file).

MDE's are designed for distribution to users in cases where you do not want
the user to have access to the code in the database. Standard distribution
practice dictates that you hide all MS Access related interface (standard
toolbars, menus, database window, special keys, etc), and use a custom form
upon startup where the user can then navigate to any part of application that
you might want them to. MDE's also strip the application of user-visible VBA
code that is used.

My experience does not extend to SQL Server (or any other backend except
access), but if I understand correctly (and I believe I do), this structure
of BE/FE files does not change regardless of what BE platform you use.

Hopefully this gives some direction related to the question at hand.

--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)

 

[Jack Leach]

An Access database is not an .exe file and cannot, in any way, be made into
an

..exe file.

Somewhere out there (the link must be at my house, because I don't seem to
have it here at the office), there is a person (MVP maybe, or at least
someone that struck me as fairly knowledgable (of a different office program,
excel if my memory serves me)), that has created a "converter" to convert an
access file (mdb or mde, I forget which), into an exe file, along with a
number of other unorthodox tools for accomplishing such strangeness for
programs of the office suite.

As far as WHAT this tool actually does (other than putting a file of exe
extension on your desktop), I have no idea. I have trouble imagining that
someone might have found a way to bypass the use of the access host
application, runtime or otherwise, in such a tool. Maybe the "converter"
merely writes an exe file which in turns executes an access file with
whatever currently registered program happens to be on the machine.

My experience with this tool consisted of 1) downloading it, 2) converting a
file, 3) looking at the file on the desktop, 4) saying "huh.. look at that,
5)deleting the file and never using the tool again.

I'll look when I get home, hopefully I can find the link. I'd be curious
for someone else's take on it.

Cheers!


--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)

 

[Jack Leach]

http://orlando.mvps.org/DBtoEXEMore.asp?IdC=Acc

quoted from the page:

"Like original format files, the EXE files created are not independent of
Access, but they allow you to define Access's properties before opening and
improve the portability and functionality of your databases with or without
macros and without macro alert."


--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)