Access Future?

[Steve]

From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[Jens Schilling]

Hi,

Steve wrote:

From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is
replaced, sometime around 2009.

Did you read the comments there ?

Quote:
--------
By Zac Woodall
Posted Wednesday 16th January 2008 17:52 GMT

I work on the team at Microsoft which implements VBA in Office and I can
tell you that VBA will absolutely continue to ship in the next version of
Office (14).

I'm not sure where Phil is getting his information, but his assertion that
we're dropping VBA support from Windows Office is false.

--------

Regards
Jens

[Tony Toews [MVP]]

"Steve" <st***@nospam.netwrote:

>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

That is totally *WRONG*.

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/

[Arch]

On Thu, 17 Jan 2008 09:35:38 -0500, "Steve" <st***@nospam.netwrote:

>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

How can that guy post something as fact that is apparently completely
wrong?

[rkc]

Steve wrote:

From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

http://blogs.msdn.com/access/archive...office-14.aspx

[Steve Brown]

From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

That's a URL that specifically references Office Mac 08.

And they've removed the speculation about Windows Office.

Access is not available for Office Mac.

Donno that any of the comments I've seen here or there have
been helpful: Have they removed VBA from Mac Excel?

"I work on the team at Microsoft which implements VBA in Office and I can
tell you that VBA will absolutely continue to ship in the next version of
Office (14)."

That just adds to my confusion. Sounds very sure of himself, but
I didn't think that Mac Office 08 was version 14 ????

Dunno what effect this will have on the PC. If you are writing
cross platform Excel applications, it may already be very late.
No obvious affect on Access, because we have never been
cross platform.

(david)
"Steve" <st***@nospam.netwrote in message
news:47**********************@cv.net...

From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said
future application development should use Visual Studio Tools for
Applications (VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[Tom van Stiphout]

On Thu, 17 Jan 2008 09:35:38 -0500, "Steve" <st***@nospam.netwrote:

I highly doubt it. You can bitch about MSFT all you want, but one
thing they understand is to be backward compatible. There is just no
way they would allow A2009 to come out and it would break all existing
VBA applications.
Please continue your rant in alt.conspiracytheories

Now I *DO* think VBA programmers need to get with the program (he, he)
and bone up on .NET programming. Here is an elegant intermedium:
http://groups.google.com/group/comp....c77f430c7402db

-Tom.

>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[Dominic Vella]

I've been doing programming for 30 years, and never been paid for it. It's
always charities and such that ask for programming. Big corporations don't
seem to be interested unless you're fresh out of uni.

Who can afford to keep buying the latest, greatest Studio software? I wish
(in my dreams). I could bone up on .NET. That would be nice, till then
MS-Access2000 is nice enough.
Dominic

"Tom van Stiphout" <no*************@cox.netwrote in message
news:au********************************@4ax.com...

On Thu, 17 Jan 2008 09:35:38 -0500, "Steve" <st***@nospam.netwrote:

I highly doubt it. You can bitch about MSFT all you want, but one
thing they understand is to be backward compatible. There is just no
way they would allow A2009 to come out and it would break all existing
VBA applications.
Please continue your rant in alt.conspiracytheories

Now I *DO* think VBA programmers need to get with the program (he, he)
and bone up on .NET programming. Here is an elegant intermedium:
http://groups.google.com/group/comp....c77f430c7402db

-Tom.

>>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said
future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[Dominic Vella]

Working at Microsoft, that would be so cool.

Dom
"Jens Schilling" <je************************@fissership.dewrote in message
news:fm*************@news.t-online.com...

Hi,

Steve wrote:

>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is
replaced, sometime around 2009.

Did you read the comments there ?

Quote:
--------
By Zac Woodall
Posted Wednesday 16th January 2008 17:52 GMT

I work on the team at Microsoft which implements VBA in Office and I can
tell you that VBA will absolutely continue to ship in the next version of
Office (14).

I'm not sure where Phil is getting his information, but his assertion that
we're dropping VBA support from Windows Office is false.

--------

Regards
Jens

[Dominic Vella]

Hey Jens

Can I make a wish list for Future VBA versions.

Particularly, I'd like to see VBA automatically write closing statements
like it already does with Sub's An Functions, even lock them if possible,
like:
- End If to automatically appear if user types If...Then (with else
statement too, as holding down delete is easier than pressing the e, the l,
the s and e keys, etc.)
- End Select to automatically appear if user types Select Case..... (with a
Case in the middle too)
- Wend to automatically appear if user types While
- Loop with Do
- Next with For
etc. etc. etc.

Or maybe add it as an editing option.

I promise not to bug you about this stuff again
:O)

Dominic

"Jens Schilling" <je************************@fissership.dewrote in message
news:fm*************@news.t-online.com...

Hi,

Steve wrote:

>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is
replaced, sometime around 2009.

Did you read the comments there ?

Quote:
--------
By Zac Woodall
Posted Wednesday 16th January 2008 17:52 GMT

I work on the team at Microsoft which implements VBA in Office and I can
tell you that VBA will absolutely continue to ship in the next version of
Office (14).

I'm not sure where Phil is getting his information, but his assertion that
we're dropping VBA support from Windows Office is false.

--------

Regards
Jens

[Jens Schilling]

Hi, Dominic

Can I make a wish list for Future VBA versions.

Sure, you may create a wish list as large as you like, as long as you
address it to MS instead of me ;-)

Regards
Jens

[Tom van Stiphout]

On Fri, 18 Jan 2008 18:55:17 +1100, "Dominic Vella"
<do***********@optusnet.com.auwrote:

The free version is pretty good:
http://www.microsoft.com/express/dow...spx#webInstall
(excuse the ugly web page)

-Tom.

>I've been doing programming for 30 years, and never been paid for it. It's
always charities and such that ask for programming. Big corporations don't
seem to be interested unless you're fresh out of uni.

Who can afford to keep buying the latest, greatest Studio software? I wish
(in my dreams). I could bone up on .NET. That would be nice, till then
MS-Access2000 is nice enough.
Dominic

"Tom van Stiphout" <no*************@cox.netwrote in message
news:au********************************@4ax.com.. .

>On Thu, 17 Jan 2008 09:35:38 -0500, "Steve" <st***@nospam.netwrote:

I highly doubt it. You can bitch about MSFT all you want, but one
thing they understand is to be backward compatible. There is just no
way they would allow A2009 to come out and it would break all existing
VBA applications.
Please continue your rant in alt.conspiracytheories

Now I *DO* think VBA programmers need to get with the program (he, he)
and bone up on .NET programming. Here is an elegant intermedium:
http://groups.google.com/group/comp....c77f430c7402db

-Tom.

>>>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said
future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[Steve]

This was not a rant, nor a bitch out of MSFT. I posted a quote from an
article, and provided the actual link. The quote was accurate, and not
taken out of context.

It was posted so people could comment on its accuracy. It took me by
surprise, since I never heard of the dropping VBA completely.

Get a grip.

"Tom van Stiphout" <no*************@cox.netwrote in message
news:au********************************@4ax.com...

On Thu, 17 Jan 2008 09:35:38 -0500, "Steve" <st***@nospam.netwrote:

I highly doubt it. You can bitch about MSFT all you want, but one
thing they understand is to be backward compatible. There is just no
way they would allow A2009 to come out and it would break all existing
VBA applications.
Please continue your rant in alt.conspiracytheories

Now I *DO* think VBA programmers need to get with the program (he, he)
and bone up on .NET programming. Here is an elegant intermedium:
http://groups.google.com/group/comp....c77f430c7402db

-Tom.

>>From http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

"VBA will disappear completely when Office 2007 for Windows is replaced,
sometime around 2009.

Microsoft announced last July it would no longer license VBA and said
future
application development should use Visual Studio Tools for Applications
(VSTA) or Visual Studio Tools for Office (VSTO)."

If you plan to be developing in the future, even in Office, it may be wise
to learn VB.Net.

Steven

[rkc]

Tom van Stiphout wrote:

On Fri, 18 Jan 2008 18:55:17 +1100, "Dominic Vella"
<do***********@optusnet.com.auwrote:

The free version is pretty good:
http://www.microsoft.com/express/dow...spx#webInstall
(excuse the ugly web page)

Calling that ugly is being kind.

[Allen Browne]

"Steve" <st***@nospam.netwrote in message
news:47**********************@cv.net...

>
It was posted so people could comment on its accuracy. It took me
by surprise, since I never heard of the dropping VBA completely.

Steve, hopefully you have caught up with the fact that the Microsoft team
has confirmed VBA will be in Access 14:
http://blogs.msdn.com/access/archive...office-14.aspx

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Steve]

Yes. That was constructively brought up in the thread after I noted the
article.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...

"Steve" <st***@nospam.netwrote in message
news:47**********************@cv.net...

>>
It was posted so people could comment on its accuracy. It took me
by surprise, since I never heard of the dropping VBA completely.

Steve, hopefully you have caught up with the fact that the Microsoft team
has confirmed VBA will be in Access 14:
http://blogs.msdn.com/access/archive...office-14.aspx

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Steve]

Yes. That was constructively brought up in the thread after I noted the
article.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...

"Steve" <st***@nospam.netwrote in message
news:47**********************@cv.net...

>>
It was posted so people could comment on its accuracy. It took me
by surprise, since I never heard of the dropping VBA completely.

Steve, hopefully you have caught up with the fact that the Microsoft team
has confirmed VBA will be in Access 14:
http://blogs.msdn.com/access/archive...office-14.aspx

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Steve]

Yes. That was constructively brought up in the thread after I noted the
article.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:47***********************@per-qv1-newsreader-01.iinet.net.au...

"Steve" <st***@nospam.netwrote in message
news:47**********************@cv.net...

>>
It was posted so people could comment on its accuracy. It took me
by surprise, since I never heard of the dropping VBA completely.

Steve, hopefully you have caught up with the fact that the Microsoft team
has confirmed VBA will be in Access 14:
http://blogs.msdn.com/access/archive...office-14.aspx

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[David W. Fenton]

Tom van Stiphout <no*************@cox.netwrote in
news:au********************************@4ax.com:

Now I *DO* think VBA programmers need to get with the program (he,
he) and bone up on .NET programming.

That's what I heard a lot when ADO came out.

Thankfully, I didn't waste one minute on ADO.

I'm not wasting any time on .NET, either.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Tony Toews [MVP]]

Arch <se*****@spam.netwrote:

>How can that guy post something as fact that is apparently completely
wrong?

Because he is a moron?

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/

[Steve]

The quote was from an article on http://www.regdeveloper.co.uk/.

Read original post.

The article was wrong. They corrected themselves, and that has been noted
in this thread, and the updated the article:

"This story has been updated. We wrongly reported Microsoft is stopping
support for VBA in Office. Thanks to Microsoft and readers who contacted us
to point out our mistake. Apologies for any misunderstanding."
http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

It seems that there were a lot of "morons" that read the article.
"Tony Toews [MVP]" <tt****@telusplanet.netwrote in message
news:ea********************************@4ax.com...

Arch <se*****@spam.netwrote:

>>How can that guy post something as fact that is apparently completely
wrong?

Because he is a moron?

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/

[David W. Fenton]

"Steve" <st***@nospam.netwrote in
news:47**********************@cv.net:

The quote was from an article on http://www.regdeveloper.co.uk/.

Read original post.

The article was wrong. They corrected themselves, and that has
been noted in this thread, and the updated the article:

"This story has been updated. We wrongly reported Microsoft is
stopping support for VBA in Office. Thanks to Microsoft and
readers who contacted us to point out our mistake. Apologies for
any misunderstanding."
http://www.regdeveloper.co.uk/2008/0...ce_mac_08_vba/

It seems that there were a lot of "morons" that read the article.

But they should have checked with Microsoft before publishing the
article. It wouldn't have taken much time to have gotten the facts
correct the first time around.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Wayne]

I realize that the status quo probably can't remain forever, but given
the millions of lines of VBA code out there in everything from home
built to professionally developed Access databases not to mention
Excel spreadsheets etc, would MS even consider dumping it in the
foreseeable future given their fairly good track record of backwards
compatibility? Surely it wouldn't be worth the bad publicity that
they would receive.

[lyle fairfield]

Wayne <cq*******@volcanomail.comwrote in news:a1216733-9521-4dde-9250-
07**********@s13g2000prd.googlegroups.com:

I realize that the status quo probably can't remain forever, but given
the millions of lines of VBA code out there in everything from home
built to professionally developed Access databases not to mention
Excel spreadsheets etc, would MS even consider dumping it in the
foreseeable future given their fairly good track record of backwards
compatibility? Surely it wouldn't be worth the bad publicity that
they would receive.

Yeah, and what if they stopped using JET in Access, and stopped including
it in their OS installations and in MDAC?

Given the millions of lines of JET SQL out there in everything from home
built to professionally developed Access databases not to mention
Excel spreadsheets etc, would MS even consider dumping it in the
foreseeable future given their fairly good track record of backwards
compatibility? Surely it wouldn't be worth the bad publicity that
they would receive.

It'll never happen, right?

[Wayne]

It'll never happen, right?

I guess time will tell.

[lyle]

On Jan 22, 1:55 am, Wayne <[e-mail]:

It'll never happen, right?

I guess time will tell.

Time has told.

Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

JET was useful for a long time. It still can be. So if MS can
terminate something useful like JET, why not terminate the archaic,
clumsy, slow, limited VBA?

I will rejoice when VBA is replaced. Anything else will be an
improvement.

[Wayne]

Got this of Wikipedia for what it's worth:

From a data access technology standpoint, Jet is considered a
deprecated technology by Microsoft. The Jet engine is no longer
distributed with the latest Microsoft Data Access Components (MDAC).
However, Jet is and will continue to be the primary database engine
for Microsoft Access. Version 2007 onwards. Access includes an
updated version of the Jet engine, separate from the one included in
Windows with MDAC, which is fully compatible with the database files
created for the generic Jet database engine. This version is
accessible only to Microsoft Access and will be updated only with
Access.

The Jet Database Engine will remain 32-bit for the foreseeable 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, except through intermediate
32-bit software that acts as a proxy for the 64 bit client.

[David W. Fenton]

lyle <ly************@gmail.comwrote in
news:44**********************************@d21g2000 prf.googlegroups.co
m:

On Jan 22, 1:55 am, Wayne <[e-mail]:

It'll never happen, right?

I guess time will tell.

Time has told.

Format your hard drive. Install Vista. Install Office 2007. Search
for JET. I think you will find nothing. JET has flown away. It IS
no more.

Er, I don't have Vista, but isn't Vista still using Jet for Active
Directory? That would mean that there are Jet 4.0 registry keys in
the registry, which means Jet is still there, and in use by OS
components.

JET was useful for a long time. It still can be. So if MS can
terminate something useful like JET, why not terminate the
archaic, clumsy, slow, limited VBA?

So far as I can tell, MS is not terminating Jet. It has branched
into the version that is managed by the Windows team, the legacy Jet
4.0 that is used in Active Directory, and the version of Jet that is
managed by the Access team, which is called the ACE, but is really
Jet 5.0.

I will rejoice when VBA is replaced. Anything else will be an
improvement.

Perl? QBasic? Javascript? Java? Lisp?

You really shouldn't make categorical statements like that, because
you don't really mean it when you say that.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Wayne]

On Jan 23, 4:18*pm, lyle <[e-mail]:

On Jan 22, 1:55 am, Wayne <[e-mail]:

Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

So are you saying that if I install Vista and then Office 2007 that I
won't be able to use Access 2007 because Jet will be non-existent?

[Tony Toews [MVP]]

lyle <ly************@gmail.comwrote:

>Time has told.

Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

It's been replaced by ACE. Upgraded for the A2007 format ACCDBs but can still access
MDBs.

>I will rejoice when VBA is replaced. Anything else will be an
improvement.

<shudder>

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/

[Tony Toews [MVP]]

Wayne <cq*******@volcanomail.comwrote:

>Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

So are you saying that if I install Vista and then Office 2007 that I
won't be able to use Access 2007 because Jet will be non-existent?

No, not at all. Lyle is incorrect. Access 2007 will still be able to read and
update A2000 MDBs.

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/

[josephlee]

On Jan 24, 4:41*pm, "Tony Toews [MVP]" <[e-mail]:

No, not at all. *Lyle is incorrect. * Access 2007 will still be able to read and
update A2000 MDBs.

I figured that he might have been, but with my rudimentary knowledge
and skill level I didn't feel that I was in a position to argue with
him. Most of you guys have forgotten more than I know about Access!

[Wayne]

On Jan 24, 4:41*pm, "Tony Toews [MVP]" <[e-mail]:

No, not at all. *Lyle is incorrect. *

I suspected that that may be the case, which is surprising.

[lyle fairfield]

"Tony Toews [MVP]" <tt****@telusplanet.netwrote in
news:ln********************************@4ax.com:

Wayne <cq*******@volcanomail.comwrote:

>>Format your hard drive. Install Vista. Install Office 2007. Search
for JET. I think you will find nothing. JET has flown away. It IS no
more.

So are you saying that if I install Vista and then Office 2007 that I
won't be able to use Access 2007 because Jet will be non-existent?

No, not at all. Lyle is incorrect. Access 2007 will still be able
to read and update A2000 MDBs.

Tony

-
Do you mean that if I:
Format my hard drive. Install Vista. Install Office 2007. Search for JET.
I WILL find files whose names include "JET"?
-
-
You wrote, "Lyle is incorrect. Access 2007 will still be able to read and
update A2000 MDBs."

The first sentence is often correct.
The second sentence is true; I might have might have said, "Access 2007 can
create and use MDBs".
But what do the two sentences have to do with each other?
-
-
The point of my original response was this:
As Microsoft has diminished Jet to the point of calling it Ace in Access,
and terminating its use by other applications, except for a few instances
where other MS technologies would be inconvenienced, then it may be quite
willing to diminish VBA; my GUESS is over the next several years and
versions of Office, VBA's use will shrivel and its name will change.
-
-
I suggest that those who want more information about JET's status do a
Google search on "JET 2007". Articles like
http://ssis.wik.is/Data_Sources/Microsoft_Office_(2007)
may be informative.

[David W. Fenton]

"Tony Toews [MVP]" <tt****@telusplanet.netwrote in
news:7m********************************@4ax.com:

It's been replaced by ACE.

AKA, Jet 5.0.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Tony Toews [MVP]]

"Dominic Vella" <do***********@optusnet.com.auwrote:

>Can I make a wish list for Future VBA versions.

<snip>

Write up your list and/or place it on a website and I'll ensure it gets placed in our
Access MVP discussion group. Microsoft will also be able to view that. However be
warned that you may never see your suggestions implemented. I've been making some
similar suggestions for a few years now.

>I promise not to bug you about this stuff again

Nah bug us.

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/

[Albert D. Kallal]

"lyle" <ly************@gmail.comwrote in message
news:44**********************************@d21g2000 prf.googlegroups.com...

On Jan 22, 1:55 am, Wayne <[e-mail]:

It'll never happen, right?

I guess time will tell.

Time has told.

Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

Wrong...I just did a clean install of vista with NO software..and JET
exists....

(in other words, I not even insalled office, or *anything* else......).

JET 4 still is included with windows, and the follwoing scrip ran on a
virgian instlal..and that means the workgroup file also must exist....
---------------
Set dbeng = CreateObject("DAO.DBEngine.36")
strMdbFile = "C:\jettest\MultiSelect.mdb"

Set db = dbeng.OpenDatabase(strMdbFile)

set tdefs = db.tabledefs

for i = 0 to tdefs.Count - 1
if left(tdefs(i).name,4) <"MSys" then
strTables = strTables & tdefs(i).name & chr(13) & chr(10)
end if
next

msgbox strTAbles
-------------------------

If you cut/paste the above into a text file (notepad), and re-name the
extension as vbs, the above script will display the tables in a mdb file
placed in a virgin vista box without ANY copy of ms-access (or office)
having been installed. virgin install...right out of the box...

JET has been, and is *still* included with vista....

strange, but a "search" of .mdw file came up empty.....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[lyle]

On Jan 25, 5:30 am, "Albert D. Kallal" <[e-mail]>
wrote:

"lyle" <[e-mail] in message

news:44**********************************@d21g2000 prf.googlegroups.com...

On Jan 22, 1:55 am, Wayne <[e-mail]:

It'll never happen, right?

I guess time will tell.

Time has told.

Format your hard drive. Install Vista. Install Office 2007. Search for
JET. I think you will find nothing. JET has flown away. It IS no more.

Wrong...I just did a clean install of vista with NO software..and JET
exists....

Did you find files whose names included "JET"?

[lyle fairfield]

"Albert D. Kallal" <Pl*******************@msn.comwrote in
news:S7jmj.4758$ow.3812@pd7urf1no:

You may not be finding the files because they might have been moved
from .dll to some type of different file in the OS (manifest files
perhaps???).

Yes, further review shows that these (jet manifest) files exist.

You can slice and dice the semantics about searching for the files.(I
can't find them either), but a TRUCK-LOAD of code that uses jet would
break if removed from vista....

It was never my contention that jet applications would not run in Vista. My
wife runs a vanilla Ms-Access 2000/Jet application in Vista almost every
day. It was my contention that JET as we have known it for many years as an
independent technology has gone from Vista. And my point is that if MS will
mess with JET it may be quite willing to mess with VBA.

Right now, you can run a 1981 copy of Visi-calc on a vista box. I can
run FoxPro 2.6 (dos) code from the late 80's on vista. And, I can run
windows 3.1 applications on Vista.

Yes, I can go back to Foxbase 1.?, even DBase III and run them.

**********
Bridging here to your previous post.

Is it possible that the absence of the mdw file indicates that you did not
instantiate "JET" DAO but rather "ACE" DAO?

[David W. Fenton]

lyle <ly************@gmail.comwrote in
news:3d**********************************@j20g2000 hsi.googlegroups.co
m:

Did you find files whose names included "JET"?

Perhaps he didn't if he failed to tweak the search to return system
files.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Tony Toews [MVP]]

"Albert D. Kallal" <Pl*******************@msn.comwrote:

>MS has a STELLAR track record in preserving your software investment, and
JET still continues to ship with windows..and vista right out of the box....

Except for VB 6.0.

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/

[Albert D. Kallal]

"lyle fairfield" <ly******@yah00.cawrote in message

Is it possible that the absence of the mdw file indicates that you did not
instantiate "JET" DAO but rather "ACE" DAO?

Yes...perhaps, good point on your part..

On the other hand, I could look up the dao property for the current "path"
to the workgroup file..and if such a property exists...I could print/display
the location, perahps I look this up...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[The Frog]

Thanks David, appreciated. I will have a hunt for the OLEDB / ADO
drivers and also any ODBC ones I can locate. There might be others as
well for languages such as Java etc...

Cheers

The Frog

[The Frog]

Okay, here is the link for the OLEDB and ODBC drivers for Office 2007
file formats:

http://www.microsoft.com/downloads/d...displaylang=en

Of course be careful of the word wrap when copying and pasting.

These apparently only work with Server 2003, Vista, and XP Service
Pack 2

Cheers

The Frog