Microsoft Access Without Jet

Why Current Attempts To Evolve Access Without Jet Lack Lustre

The whole issue can get quite emotionally charged because evolving MicrosoftAccess without the JetDatabaseEngine is not a simple matter of technology, it drastically affects the livelihood, joie de vivre of some very passionate people.

Since Jet is intertwined with the .mdb format, let's discuss the new format - the .adp - which has no Jet. After some development experience with .adp, here are some points of concern:

To understand about some of these breaks in transparency read: "Microsoft Access Projects with Microsoft SQL Server" by Microsoft Press (there is a story about why "Microsoft" has to be in every name <grin>) by Albrecht and Nicol.

http://www.amazon.com/exec/obidos/tg/detail/-/0735610029/qid=1030840613/sr=1-2/ref=sr_1_2/104-0391853-8557530?v=glance&s=books

-- AnandaSim


But See InspectEvalFileFormat

--PhlIp

To each, his own

But seriously, the Dictionary object is also available in VisualBasicForApplications, VisualBasic or anything that can consume the VbScript - ScriptingDictionary? object. This is equivalent to the Perl associative array and real cool.

--AnandaSim

Can VB inspect and eval? I don't know. You might want to check out WhyVisualBasic or CategoryVisualBasic .

EditText of this page (last edited June 25, 2005) or FindPage with title or text search