It's a shame that Microsoft has put Jet into obsolescense in favor of MSDE which is a memory hog and a nightmare to install. MSDE is a 70 meg. package with only the server component and no sufficient client-software. Installing under Windows XP sp2 is a worse nightmare because of security problems, aaarrgh! It's installer is a really bad one, since it's worse than DOS installers, because it only works correctly if the input at the commandline is meaningful. A dialog based installer is expected and the installer is a visiting card of the application. If this is already poor, then I think the application might be poor too. MSDE isn't poor at all, but the installer is. :-(
I plea for a new Jet engine!
There are some ways to realise this:
Microsoft could put Jet into open-source, so the community can correct and/or extend the engine. The following things should then be possible:
1: Written udf functions within Access could then be available to ANY program, including .NET apps.
2: Define stored procedures and triggers by calling udf functions.
3: SQL mode udf, stored procedures (not only querydefs!!) and triggers.
Microsoft could create a new proprietary JetV (version 5) engine written in .NET, so the VBA bulk gets out of there. I find .NET much cleaner to read than unmanager C++. Native C++ can lead to numerous hard to find stinging bugs whilst .NET alerts the program with understandable exception messages. .NET rules!
I plea for a new Jet engine!
There are some ways to realise this:
Microsoft could put Jet into open-source, so the community can correct and/or extend the engine. The following things should then be possible:
1: Written udf functions within Access could then be available to ANY program, including .NET apps.
2: Define stored procedures and triggers by calling udf functions.
3: SQL mode udf, stored procedures (not only querydefs!!) and triggers.
Microsoft could create a new proprietary JetV (version 5) engine written in .NET, so the VBA bulk gets out of there. I find .NET much cleaner to read than unmanager C++. Native C++ can lead to numerous hard to find stinging bugs whilst .NET alerts the program with understandable exception messages. .NET rules!