Better replacement of Microsoft Jet for 64-bit platform

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

Hi,

What is the better choice for replacement of Microsoft Jet v4.0. I
need this replacement because Microsoft Jet isn't support in 64-bit
platform. My current BD are writen in MDB files.

Here is some alternative that I found :

SQL Server Everywhere (not yet support 64-bit)
VistaDB
Sybase SQL Anywhere

Regards,
Eric
 
What is the better choice for replacement of Microsoft Jet v4.0.
I need this replacement because Microsoft Jet isn't support in
64-bit platform. My current BD are writen in MDB files.

Here is some alternative that I found :

SQL Server Everywhere (not yet support 64-bit)
VistaDB
Sybase SQL Anywhere
Click to expand...

I'm confused. Windows Active Directory uses Jet for its data store.
If Jet can't run on 64-bit Windows, then what is used for the data
store in Active Directory?

Where'd you get the information that Jet can't run on 64-bit
Windows?
 
i run MDB under Vista x64 with only a couple of bugs...

in general; JET doesn't utilize Ram-- it doesn't run faster if you have
512mb than if you had 128; I reccomend using SQL Server 2005 Express..
I will be happy when Access 2007 is for sale

-Tom
 
David said:
This article lists Jet files for 64-bit Windows Server 2003:

http://support.microsoft.com/kb/870753/en-us

so, I think you are mistaken that Jet can't run on 64-bit Windows.
Click to expand...

Jet can run on Windows XP x64 for example, but in 32-bits mode. There
is only a 32-bits version of this driver.

"The Jet Database Engine will remain 32-bit only for the forseeable
future. Microsoft has no plans to natively support Jet under 64-bit
versions of Windows. This means that native 64-bit applications (such
as the 64-bit versions of SQL Server) cannot access data stored in MDB
files through ODBC, OLE DB, or any other means." from
http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine

"Jet: Starting with version 2.6, MDAC no longer contains Jet
components. In other words, MDAC 2.6, 2.7, 2.8, and all future MDAC
releases do not contain Microsoft Jet, Microsoft Jet OLE DB Provider,
or the ODBC Desktop Database Drivers." from
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/data_mdacroadmap.asp

Eric
 
and THUS; JET IS OBSOLETE

I don't see the same article with ADP or ADO or anything

lose the act you ****ing posers; MDB is dogmeat; it's been obsolete for
10 years
 
Jet can run on Windows XP x64 for example, but in 32-bits mode.
There is only a 32-bits version of this driver.

"The Jet Database Engine will remain 32-bit only for the
forseeable future. Microsoft has no plans to natively support Jet
under 64-bit versions of Windows. This means that native 64-bit
applications (such as the 64-bit versions of SQL Server) cannot
access data stored in MDB files through ODBC, OLE DB, or any other
means." from
http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine
Click to expand...


That claim is not documented by any Microsoft sources, and I wonder
if it is out of date.

The page is also incorrect in what it says about the the future of
Access/Jet:

However, Jet is and will continue to be the primary database
engine for Microsoft Access. In fact, Jet is essentially going
back to its roots with Access 2007, by being distributed (and
supported) only within Access.

This is *WRONG*. The Jet db engine now has two versions, one of
which is a Windows component maintained by the SQL Server team (the
traditional plain old Jet engine, the one used for Active Directory)
and the other maintained by the Access team, which branches from the
other version and can add new features. The citation of Eric
Rucker's blog for this claim is completely misleading -- he does not
say that Jet is now used only in Access. Instead, he says that there
are *two* versions of Jet, and the one maintained by the SQL Server
term is not being upgrade.

This is not news!

This is what we've been told since the release of Jet 4!

So, I have a problem trusting anything posted in the Wikipedia
article, as I can quickly identify inaccuracies without needing to
read more than a paragraph away from the quotation above.

(I've posted questions on both these issues on the Wikipedia talk
page and we'll see what they come up with in response)
"Jet: Starting with version 2.6, MDAC no longer contains Jet
components. In other words, MDAC 2.6, 2.7, 2.8, and all future
MDAC releases do not contain Microsoft Jet, Microsoft Jet OLE DB
Provider, or the ODBC Desktop Database Drivers." from
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dn
mdac/html/data_mdacroadmap.asp
Click to expand...

That last one is not even close to being news. It's been the case
for a couple of years now. And it has nothing to do with the 64-bit
issue.
 
well it still illustrates that Microsoft doesn't give a flying SHIT
about DAO and JET.

DAO and JET are retarded.
I can do anything in ADO that you punk ass lamers can do in DAO.. and I
don't have to rewrite everything I do when my engine starts sputtering.

CREATE TABLE TABLENAME
CREATE INDEX INDEXNAME
CREATE PROCEDURE PROCNAME
CREATE VIEW VIEWNAME

Select Name from Sysobjects where Xtype = 'P'
Select Name from Sysobjects where Xtype = 'V'
Select Name from Sysobjects where Xtype = 'U'


****ing wusses-- go out and learn a real programming language-- MDB and
DAO and JET is for lamers and retards.

This newsgroup-- Microsoft.Public.Access _BELONGS_ to Access Data
Projects.

One of these days they'll make a new group called

Microsoft.Public.Access.Obsolete.MDB

ROFL

Grow some balls kids; MDB is for weenies
 
RE:
However, Jet is and will continue to be the primary database
engine for Microsoft Access. In fact, Jet is essentially going
back to its roots with Access 2007, by being distributed (and
supported) only within Access.


JET _NEVER_WAS_AND_NEVER_WILL_BE_ the primary engine



When you go FILE, NEW you have '1 option' to create a new Access
Application... and '2 options' to create Access Projects.

Because of this; Projects are the 'primary database engine' for
Microsoft Access
 
(e-mail address removed) wrote in
RE:
However, Jet is and will continue to be the primary database
engine for Microsoft Access. In fact, Jet is essentially going
back to its roots with Access 2007, by being distributed (and
supported) only within Access.


JET _NEVER_WAS_AND_NEVER_WILL_BE_ the primary engine
Click to expand...

Eh? An MDB application has all of its Access objects stored in a Jet
database. The wizards are MDEs that store everything in Jet tables.
When you go FILE, NEW you have '1 option' to create a new Access
Application... and '2 options' to create Access Projects.
Click to expand...

In what version? None of the versions I have work that way.
Because of this; Projects are the 'primary database engine' for
Microsoft Access
Click to expand...

You're an obvious idiot.
 
go FILE, NEW and tell me what you see

Blank Database
Blank Data Access Page
Project ssing existing data
Project using new data
From Existing File
Click to expand...

lets' refer to them as #1, #2, #3, #4, #5, ok?

1 = MDB
2 = DAP (ADP _OR_ MDB)
3 = ADP
4 = ADP
5 = ADP _OR_ MDB

so lets' cut out the ties and we get

1 = MDB
3 = ADP
4 = ADP

and please; pray tell me-- which one has more options.. ADP or MDB?

thus ADP is the DEFAULT ENGINE
 
I agree; 2 is more than 1-- so where do you get off saynig that MDB is
the 'default engine'

it's not the default engine; it is the OBSOLETE engine



go FILE, NEW and tell me what you see

Blank Database
Blank Data Access Page
Project ssing existing data
Project using new data
From Existing Filelets' refer to them as #1, #2, #3, #4, #5, ok?
Click to expand...

1 = MDB
2 = DAP (ADP _OR_ MDB)
3 = ADP
4 = ADP
5 = ADP _OR_ MDB

so lets' cut out the ties and we get

1 = MDB
3 = ADP
4 = ADP

and please; pray tell me-- which one has more options.. ADP or MDB?

thus ADP is the DEFAULT ENGINE


(e-mail address removed) wrote in
Click to expand...
Eh? An MDB application has all of its Access objects stored in a Jet
database. The wizards are MDEs that store everything in Jet tables.
Click to expand...
In what version? None of the versions I have work that way.
Click to expand...
You're an obvious idiot.
Click to expand...
Click to expand...
 
I agree; Access Data Projects are a superior technology and everyone
should be using them

-Larry
 
I agree; Access Data Projects are a superior technology and everyone
should be using them

-Larry
Click to expand...

Actually Aaron masquerading (unconvincingly) as Larry.

John W. Vinson[MVP]
 
what are you talking about?

I just see 'Larry Linson' and -Larry

I think that Larry woke up and said holy crap the year is 2006 and SQL
Server is bigger, better, faster, easier, more powerful and the same
price as MDB

-Tom
 
Back
Top