ol**@ylm.se wrote:
So folks: Do you think that I am doing the right thing moving to Visual
studio dot.net?
I think you have done the right thing moving away from Access.
There may not be so many great places to move.
In the long run it may not have been wonderful for the developer that MS
bought FoxPro, that CA bought Clipper. Who knows what marvels we might
have now had these products made the move to a GUI by themselves?
I may take a another look at FoxPro, 12 years after I abandoned it. I'm
looking at various "J" things.
I'm beginning to think that all the hoopla about client-server dbs like
MS-SQL may be just that, hoopla, and that for many developers the use of
file dbs, with home-grown security may be allow superior development.
The logic of combining data, indexes, procedures in the same file has
lost its validity with me. Why? Huh? To protect us from ourselves?
I am very disillusioned with MS.
--
--
Lyle
--
From ADO28.chm
Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft® Data
Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.
ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers
instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in
the future, whereas MSDASQL will not have any new features added to it,
will not be available on 64-bit, and will not be accessible from the OLE
DB NET Data Provider.
Remote Data Services (RDS)
Remote Data Services (RDS) is a proprietary Microsoft mechanism for
accessing remote data across the Internet or intranet. Microsoft is now
shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0
that enables you to access remote data using an open, XML-based
standard. Given the availability of the SOAP Toolkit 2.0, you should
migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample
code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
Recordsets.
Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
Engine, and plans no new releases or service packs for this component.
As a result, the Jet and Replication Objects (JRO) is being deprecated
in this release and will not be available in any future MDAC releases.
.....