Convert Access database into application??

[Tammy]

Hello all,

We are a small office currently running Office XP - 5 of our staff are
sharing a simple/small Access XP database. We are replacing the workstations
and getting them pre-installed with Office 2007 Basic - we really don't need
Professional on all boxes - plus we want to save $$.

These 5 staff will still require Access and it might be cheaper for us to
just buy them the Access 2007 upgrade package - less $$ than buying the
Professional version.

I would love to not do this if possible so checking to see if anyone knows
another way of accomplishing this - for example - can I somehow create an
application/program from the database and store the data in one place and the
users just one an .exe from their workstations? Our developer is too busy
right now to do anything for us.

Thanks so much for any advice/tips you might have!

Tammy

 

[calVie]

http://www.microsoft.com/downloads/...FamilyID=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed

 

[Arvin Meyer [MVP]]

You will need 1 copy of Office Professional to make design changes and
create forms and reports. You will also need it to make the conversion and
do the testing from 2003 to 2007.

I would buy that machine/Office Pro first and convert and test the app. Lots
of things that are done in the full-version cannot be done with the runtime,
so you may have to incorporate those features into your application. Test
THOROUGHLY with all users first. If it works the runtime will be your
answer, if it doesn't you'll need to spend the extra $90 to $100 for the
full version.

http://www.microsoft.com/downloads/...FamilyID=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed

 

[a a r o n . k e m p f]

if you have _ANY_ Access application-- and you tink that someone would
want to buy it-- I think that the best arrangement (for everyone) is
this:
a) upsize to SQL Server
b) keep it hosted at your location
c) when they stop paying, shut off their security

There is no such thing as a professional developer that actually ships
products using Jet databases.
Jet has been obsolete for a decade; and it won't even run on X64

-Aaron

 

[Tony Toews [MVP]]

Note that Aaron's answer to just about every question is SQL Server
and ADPs. No matter how appropriate his answer.

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's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Aaron Kempf knows nothing]

shut off a a r o n . k e m p f

 

[Tom Wickerath]

and it won't even run on X64

Really? Please explain the existance of this valid registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0

Hint: When you install Access on a 64-bit machine, this key is written to
the registry. I have Access 2007 installed on a Vista 64-bit machine.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[David W. Fenton]

=?Utf-8?B?VG9tIFdpY2tlcmF0aA==?= <AOS168b AT comcast DOT net> wrote
in
[Aaron:]

Really? Please explain the existance of this valid registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0

Hint: When you install Access on a 64-bit machine, this key is
written to the registry. I have Access 2007 installed on a Vista
64-bit machine.

To be fair, Aaron has a partially valid point -- Jet is not 64-bit
and runs under the 32-bit emulation layer. This doesn't mean that
Jet/Access won't run, but it does mean that there could be potential
problems and that the advantages of 64-bit operation are not going
to be present when running a Jet/Access application.

I don't think it matters much -- Access 2 is still really nice
running on modern versions of Windows, for instance -- but he thinks
it is evidence that Access is obsolete.

I wonder what MS will do as more and more users move to 64-bit
Windows. I expect that ACE will be updated to run 64-bit and Jet 4
will remain 32-bit. Since ACE is backwardly-compatible with Jet 4,
then it will become the preferred engine on 64-bit Windows for
working with Jet 4 and earlier data. The only loss is that Jet 4
will continue to be installed with the OS, and so if you're
depending on that to get Jet support, you won't have 64-bit
operation.

Is there some supported way to install the ACE by itself without
having a developer license to distribute it?

The other question is whether the Windows team will continue to
bundle Jet 4 as an OS component and *not* update it for 64-bit
Windows. It's not entirely clear to me why Jet 4 is an OS component
-- the old argument was that Jet 4 was used as the data store for
Active Directory, but I've since found out that AD's data store is
the Exchange version of Jet, not the Access version (i.e., Jet blue
instead of our old trusty Jet red). Nobody that I've discussed this
with seems able to explain what Jet 4 is doing. My surmise is that
it is used as the programmatic interface to the Jet blue ISAM, since
Jet blue has no data interface DLLs of its own. But I'm just
guessing on that.

So, MS would be faced with the choice of updating Jet 4 to native
64-bit, or with replacing it with something else. I'm not going to
speculate as to which direction the Windows team will choose.

 

[James A. Fortune]

So, MS would be faced with the choice of updating Jet 4 to native
64-bit, or with replacing it with something else.

Maybe Microsoft will simply keep Access hobbled to Wow64 .

James A. Fortune
(e-mail address removed)

WinFS uses a relational engine, which is derived from SQL Server 2005...

....but it suffered from significant performance issues.

....in November 2006 Steve Ballmer announced that WinFS was still in
development, though it was not clear how the technology was to be delivered.

-- http://en.wikipedia.org/wiki/WinFS

 

[Tom Wickerath]

Hi David,

To be fair, Aaron has a partially valid point....

Not really, because he did not qualify his response. He stated "and it won't
even run on X64", which is clearly not true. Yes, I'm fully aware that it is
running under an emulation layer, and that one is not getting the benefit of
64-bit. But, it does run. That was my point. Just *trying* to keep Aaron
honest, if that's even possible ;-)


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[David W. Fenton]

=?Utf-8?B?VG9tIFdpY2tlcmF0aA==?= <AOS168b AT comcast DOT net> wrote
in
[me:]

Not really, because he did not qualify his response. He stated
"and it won't even run on X64", which is clearly not true. Yes,
I'm fully aware that it is running under an emulation layer, and
that one is not getting the benefit of 64-bit. But, it does run.
That was my point. Just *trying* to keep Aaron honest, if that's
even possible ;-)

Sure -- the way he stated it was in error, but there is an
underlying issue that gives a lot of people pause. I don't think
people should worry about it (as outlined in my post), but I don't
think it's an invalid concern. And it's that fact that I'm willing
to give a tiny, teeny-weeny bit of credit to Aaron for his intent.

Now, it may very well be that he didn't have any good intentions and
just wanted to tear down Jet (very likely, in fact), but I'm willing
to find hope anywhere I can.