Run Time Version

[Morley]

1. Is the run time version a self-contained file which includes Access files
and a database or are there separate Access files and a database (.mdb) file?

2. If the database file is separate, can other database files (.mdb) be run on
a machine that has only the run time version installed?

Thanks,

Morley

[Alan Webb]

Morley,
Access runtime is a gimped version of Access that has the bits needed to
change the design of things stripped out. All Access .mdb files can be
saved as .mde files. An .mde is as close to a compiled executible
application you are going to get--though there has been plenty here about
what others have done to write something in C# or VB.NET that walks & talks
like a commercial application. If runtime is present, any Access database
can be run on that machine but no changes to the design of stuff can be
made.

"Morley" <ma*****@earthlink.net> wrote in message
news:1V*******************@newsread3.news.atl.eart hlink.net...

1. Is the run time version a self-contained file which includes Access files and a database or are there separate Access files and a database (.mdb) file?
2. If the database file is separate, can other database files (.mdb) be run on a machine that has only the run time version installed?

Thanks,

Morley

[Morley]

Alan,

Thank you for responding!

So let's see if I got what you said correct --
Access runtime stands alone on a machine. That machine then can run any Access
..mdb or .mde file installed on the machine as long as the version matches the
run time. No design changes to a database can be made on that machine.

If the database needs revised, is it just a simple matter of moving the database
to a machine with the full version of Access, make the revisions there and save
the file back to the machine with the run time version?

Now how does a split database work where the FE is on the machine with the run
time and the BE is on a network. Must Access or a runtime be installed on the
network?

Morley
"Alan Webb" <kn*****@hotmail.com> wrote in message
news:k9****************@news.uswest.net...

Morley,
Access runtime is a gimped version of Access that has the bits needed to
change the design of things stripped out. All Access .mdb files can be
saved as .mde files. An .mde is as close to a compiled executible
application you are going to get--though there has been plenty here about
what others have done to write something in C# or VB.NET that walks & talks
like a commercial application. If runtime is present, any Access database
can be run on that machine but no changes to the design of stuff can be
made.

"Morley" <ma*****@earthlink.net> wrote in message
news:1V*******************@newsread3.news.atl.eart hlink.net...

1. Is the run time version a self-contained file which includes Access

files

and a database or are there separate Access files and a database (.mdb)

file?

2. If the database file is separate, can other database files (.mdb) be

run on

a machine that has only the run time version installed?

Thanks,

Morley

[Tony Toews]

"Morley" <ma*****@earthlink.net> wrote:

So let's see if I got what you said correct --
Access runtime stands alone on a machine. That machine then can run any Access
.mdb or .mde file installed on the machine as long as the version matches the
run time. No design changes to a database can be made on that machine.
Correct.
If the database needs revised, is it just a simple matter of moving the database
to a machine with the full version of Access, make the revisions there and save
the file back to the machine with the run time version?
More likely, and mandatory if an MDE, you'd work on the MDB elsewhere on a system
with a full version of Access and then copy it to the client system.
Now how does a split database work where the FE is on the machine with the run
time and the BE is on a network. Must Access or a runtime be installed on the
network?

On the network server, no. There is no need for Access to be installed on the
server. If it was a SQL Server based BE then you'd need SQL Server installed on the
server.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Tony Toews]

Tony Toews <tt****@telusplanet.net> wrote:

If the database needs revised, is it just a simple matter of moving the database
to a machine with the full version of Access, make the revisions there and save
the file back to the machine with the run time version?

More likely, and mandatory if an MDE, you'd work on the MDB elsewhere on a system
with a full version of Access and then copy it to the client system.

I specifically created the Auto FE Updater utility so that I could make changes to
the FE MDE as often as I wanted and be quite confident that the next time someone
went to run the app that it would pull in the latest version. For more info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Morley]

Tony,

You said something here that I never knew and I have to confirm it with you ---

You mean to say that in a typical FE/BE database where the BE is on a server,
Access does not have to be on the server and the links will work fine?

Does version (97 and after) make any difference?

Morley

PS Thanks for the info on Auto FE Updater
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:lp********************************@4ax.com...

"Morley" <ma*****@earthlink.net> wrote:

So let's see if I got what you said correct --
Access runtime stands alone on a machine. That machine then can run any Access.mdb or .mde file installed on the machine as long as the version matches the
run time. No design changes to a database can be made on that machine.
Correct.

If the database needs revised, is it just a simple matter of moving the databaseto a machine with the full version of Access, make the revisions there and savethe file back to the machine with the run time version?

More likely, and mandatory if an MDE, you'd work on the MDB elsewhere on a

system with a full version of Access and then copy it to the client system.

Now how does a split database work where the FE is on the machine with the runtime and the BE is on a network. Must Access or a runtime be installed on the
network?
On the network server, no. There is no need for Access to be installed on

the server. If it was a SQL Server based BE then you'd need SQL Server installed on the server.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Scott McDaniel]

"Morley" <ma*****@earthlink.net> wrote in message
news:ev*****************@newsread2.news.atl.earthl ink.net...

Tony,

You said something here that I never knew and I have to confirm it with you ---
You mean to say that in a typical FE/BE database where the BE is on a server, Access does not have to be on the server and the links will work fine?

That's correct. The server does not need Access installed IF all it's doing
is provide disc space for the tables. All processing in an Access
application is done by the FE in a FE/BE setup.
Does version (97 and after) make any difference?
No.

Morley

PS Thanks for the info on Auto FE Updater
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:lp********************************@4ax.com...

"Morley" <ma*****@earthlink.net> wrote:

So let's see if I got what you said correct --
Access runtime stands alone on a machine. That machine then can run any Access.mdb or .mde file installed on the machine as long as the version matches therun time. No design changes to a database can be made on that machine.
Correct.

If the database needs revised, is it just a simple matter of moving the databaseto a machine with the full version of Access, make the revisions there and save

the file back to the machine with the run time version?
More likely, and mandatory if an MDE, you'd work on the MDB elsewhere on a system

with a full version of Access and then copy it to the client system.

Now how does a split database work where the FE is on the machine with

the runtime and the BE is on a network. Must Access or a runtime be installed

on thenetwork?

On the network server, no. There is no need for Access to be installed

on the

server. If it was a SQL Server based BE then you'd need SQL Server

installed on the

server.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Tony Toews]

"Morley" <ma*****@earthlink.net> wrote:

You said something here that I never knew and I have to confirm it with you ---

You mean to say that in a typical FE/BE database where the BE is on a server,
Access does not have to be on the server and the links will work fine?
Correct. The server is acting as a file server just as though it were serving Word,
Excel or dBase files.
Does version (97 and after) make any difference?

No.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm