New Access Version?

On Tue, 18 Jan 2005 18:57:26 GMT, "Neil Ginsberg" wrote:

If you do a lot of VBA coding, there are some improvements that I now find
it
hard to do without when working in A97. Custom events,

Custom events? Haven't seen that in A2000. What are they?

In any class module you create, you can define events, and other objects that
have references to that class defined using WithEvents, can receive calls to
those events from the object that raises it. It's sort of a call-back
mechanism.

On Tue, 18 Jan 2005 21:16:14 GMT, Tony Toews wrote:

"Arvin Meyer" wrote:

I think you'll find that both Access 2002 and 2003 are significantly more
reliable, especially during development, than Access 2000.

Agreed. I found that doing work in A2000 a form would corrupt about once a week or
so. A2003 hasn't had this problem at all.

Just one warning, though. Open a database with VBA code in A2003, then open
it again in XP, and it's corrupted for sure. If you go to A2K3, be sure to do
all users at once!

So they're not really events, per se, but routines within a class module
that are called, right?

"Steve Jorgensen" wrote in message
...
On Tue, 18 Jan 2005 18:57:26 GMT, "Neil Ginsberg"
wrote:

If you do a lot of VBA coding, there are some improvements that I now
find
it
hard to do without when working in A97. Custom events,

Custom events? Haven't seen that in A2000. What are they?

In any class module you create, you can define events, and other objects
that
have references to that class defined using WithEvents, can receive calls
to
those events from the object that raises it. It's sort of a call-back
mechanism.

sorry, a little naive to the correct etiquette
in a rush

h

"Bri" wrote in message news:PRbHd.112592$6l.22249@pd7tw2no...
H,

Please do NOT attach binaries to posts in non-binary newsgroups,
particularly 500+kb bmp files that could have been done as a 30kb jpg.

Thanks,

Bri

H wrote:
Just some thoughts

"David W. Fenton" wrote in message
28.78...
"H" wrote in :

It's safe to say that Microsoft want to drop
support for jet and make MSDE the default database engine (we know
it can be installed silently and without user input).

That would be lunacy of the highest sort for them to do so.

It would mean the dropping of the MDB format, since IT'S A FRIGGING
JET DB.


The format would be ADP

Furthermore, Jet is not dead at all -- it's running
ActiveDirectory's data store, for instance (this is why from Win2K
on the Jet 4 DLLs are protected OS files).


I understood that SQL Server was used in Server 2003.

Jet will never be dropped unless Access completely drops all legacy
support. It may be dropped as the default DB engine, but that would
be stupid as well, since it would mean double workset (i.e., to open
an MDB you have to have Jet loaded).


The default format will be an ADP.

Jet will (one day) disappear.

Jet's a big headach to MS.

Let's hope that MS have a momentary lapse of reason and give us Jet.Net
(Here's hoping).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

"Tony Toews" wrote in message
...
"H" wrote:

t's safe to say that Microsoft want to drop
support for jet and make MSDE the default database engine (we know it can
be
installed silently and without user input). X

Want to drop support for jet? Possibly. But they never will. It's in
way too many
systems now.

Make MSDE the default database engine? That's fine by me so long as it's
about as
easy to use as Jet.

Microsoft are not afraid to rip up the rule book and direct you to the
nearest Microsoft Sponsored Online Book Store.



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

"Steve Jorgensen" wrote in message
...

Just one warning, though. Open a database with VBA code in A2003, then
open
it again in XP, and it's corrupted for sure. If you go to A2K3, be sure
to do
all users at once!

I wouldn't say "for sure" This corruption is actually quite rare. It is
alleviated by compiling 2002 databases before saving, or not using both to
develop. I have never seen this corruption except during development.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

A number of new features in ASP .NET 2.0, such as the Membership Service,
use the Jet data provider by default (though they are capable of using other
providers). See
http://msdn.microsoft.com/msdnmag/is...w/default.aspx

I hardly think Microsoft would be doing that if they expected Jet to go away
any time in the foreseeable future.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.


"David W. Fenton" wrote in message
28.78...
"H" wrote in :

It's safe to say that Microsoft want to drop
support for jet and make MSDE the default database engine (we know
it can be installed silently and without user input).

That would be lunacy of the highest sort for them to do so.

It would mean the dropping of the MDB format, since IT'S A FRIGGING
JET DB.

Furthermore, Jet is not dead at all -- it's running
ActiveDirectory's data store, for instance (this is why from Win2K
on the Jet 4 DLLs are protected OS files).

Jet will never be dropped unless Access completely drops all legacy
support. It may be dropped as the default DB engine, but that would
be stupid as well, since it would mean double workset (i.e., to open
an MDB you have to have Jet loaded).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

On Wed, 19 Jan 2005 08:21:23 GMT, "Neil Ginsberg" wrote:

So they're not really events, per se, but routines within a class module
that are called, right?

They're definitions of methods a containing object can implement that the
contained object can invoke without having an explicit reference to the
container or knowing what object that is.

Sorry - that's right. It happens if you edit the code in A2K3. I have not
seen that compiling in A2K2 before saving helps since I always do that.

On Wed, 19 Jan 2005 07:04:35 -0500, "Arvin Meyer" wrote:

"Steve Jorgensen" wrote in message
.. .

Just one warning, though. Open a database with VBA code in A2003, then
open
it again in XP, and it's corrupted for sure. If you go to A2K3, be sure
to do
all users at once!

I wouldn't say "for sure" This corruption is actually quite rare. It is
alleviated by compiling 2002 databases before saving, or not using both to
develop. I have never seen this corruption except during development.