Access 12 and .NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Can anybody on this board inform me what access 12 will look like?
Which are the new features?
Will we be able to use our .NET libs(intellisens for methods and properties)
in VBA or even better will we be able to code with a .NET language against
the access engine?
 
JaRa said:
Can anybody on this board inform me what access 12 will look like?
Which are the new features?
Will we be able to use our .NET libs(intellisens for methods and properties)
in VBA or even better will we be able to code with a .NET language against
the access engine?
Click to expand...


Excellent question!

Unfortunately, anyone that might know the answer would be
under a Non-Disclosure Agreement so they would not be
allowed to answer it. When MS feels the A12 feature list is
firm enough for public disclosure, you will be able to find
it on their web site or summaries on various magazine sites.
 
I'm looking forward to it.
So for now, as far as Access goes, it's .not or .notyet? :-)

Immanuel Sibero
 
:-)

That might be an accurate description, but then it might
not ;-)

Seriously, even the devlopers working on a feature can not
guarantee that it will end up in the final product. Even in
the unlikely scenaraio of all developers doing a perfect job
on their piece. the integration phase that brings all the
features together may uncover a conflict that can not be
resolved in a reasonable time frame. The usual way to deal
with the product so it can proceed in the face of that kind
of conflict is to drop the least important cause of the
conflict. (A major delay in the product's ship date is
rarely a viable option.)

OTOH, Word and Excel had a lot of VS features included in
Office 11, so I think it's fair to hope that something along
those lines would be in Access 12.
 
OTOH, Word and Excel had a lot of VS features included in
Office 11, so I think it's fair to hope that something along
those lines would be in Access 12.
Click to expand...

What is VS?

Tim F
 
refered to Visual Studio 2003 in this case

Visual Studio 2005 is gonna be a beast LOL.

Since Office 2003 the .NET architecture is implemented for Excel and Word
now we are hoping Access catches up in the Near Future.
Why? Not because VBA is bad, but it has it's limits. e.g. communication with
api dlls is not necessary anymore with the .net framework at hand.
Basically MS's goal is to abstract the WIN apis for developers by making
them accessible through the .NET framework.
The benefit is that with this framework they will be able to rewrite the
basic apis without us knowing and stay backwards compatible (MS rule don;t
break any code)
But this is still 10 years from now.

- Raoul
 
Visual Studio 2005 is gonna be a beast LOL.
Click to expand...

Is that a good laugh or a bad laugh?
Since Office 2003 the .NET architecture is implemented for Excel and
Word now we are hoping Access catches up in the Near Future.
Click to expand...

I have to confess that the last programming environment I understood was
VB5... After that all the prices got silly and programming for fun went
out the window. I really hope they are not going to do the same for
scripting in VBA/ VBS. Perhaps I will end up with Delphi and PERL after
all for doing little "I need this now" jobs.
Why? Not because VBA is bad, but it has it's limits. e.g.
Click to expand...

Another confession: I am not aware of being limited by VBA - if anything
its capabilities go way beyond what I want in lots of directions. I do
see that this dot-Net stuff means something to organisations that create
big applications for a living, but it's a smack in the face for those of
us that started computing in the sixties and are kind of used to having
to use quick and simple tools for solving quick and simple problems.
But this is still 10 years from now.
Click to expand...

If I really thought it was going to be that long before another version
of Office, I'd be a much happier guy...


All the best


Tim F
 
MS is gonna support this community of hobby programming also by introducing
the express versions of development environments.

Check on www.msdn.com

- Raoul

ps it was a good laugh, i'm totally in for DotNet
 
Microsoft should ask us what we want. Is there a way to participate in this
process ?

..NET integration should be the no 1 on priority list. I think everyone
agrees that MS is overdue to make a public commitment to move Access back on
the .NET track.

henry
 
Henry,

Although I mainly develop within the .Net framework currently beta2 of
VS2005, great product!, I personally feel that Access should wait a while
before jumping in on the .Net world. Otherwise the same situation that is
going on with VB6 will happen, you will cut off all those hobist developers
who know and understand vba/vb. I feel the developers of Access should not
be thinking of making Access .Net compatible, they should focus on making
the best desktop database better in terms of
productivity/features/performance/storage. .Net is a radically different
beast to traditional vb/vba this was proven when the .Net framework first
came out and there was that import vb project tool that never got it right,
to do a proper job start again from scratch.

Don't get me wrong I think .Net is great I just don't think the access
community is ready for it, too many hobbits programmers that will be left in
the cold.

Just my thoughts.....
 
Sorry to all the hobbits I was not referring to you, my spell checker
stuffed me.
 
Alex said:
Although I mainly develop within the .Net framework currently beta2 of
VS2005, great product!, I personally feel that Access should wait a while
before jumping in on the .Net world. Otherwise the same situation that is
going on with VB6 will happen, you will cut off all those hobist developers
who know and understand vba/vb. I feel the developers of Access should not
be thinking of making Access .Net compatible, they should focus on making
the best desktop database better in terms of
productivity/features/performance/storage. .Net is a radically different
beast to traditional vb/vba this was proven when the .Net framework first
came out and there was that import vb project tool that never got it right,
to do a proper job start again from scratch.

Don't get me wrong I think .Net is great I just don't think the access
community is ready for it, too many hobbits programmers that will be left in
the cold.
Click to expand...


My thoughts are that incorporating most of VS in Access
would be nice, but that the whole .Net thing would be a real
stretch for A12.

MS has repeatedly stated that what's in A12 is still in flux
and nothing can be said conclusively at this time beyond the
plan being for a lot of major improvements.
 
Back
Top