We're in the process of going through Platinum testing on our
Marietta PDE (tm) product.
The only open issue I'm currently aware of is the support of Find.
PDE is software for rapidly developing and deploying business
applications (Order Entry, Inventory, Fixed Assets, etc.)
It has a high performance database system written in C++
that is extremely fast and supports large record counts.
(We've got some customers with databases with over 50,000
records, and 10,000 to 25,000 record item databases are very common)
The downside of this from the support of Find is:
1) C++ uses Globals, and Find doesn't allow Globals and hence
Find doesn't support C++
2) Even if we could support Find, the last thing that someone using
Find expects is to hit is the large databases that our product
typically uses.
Most people don't want to chew through a 25,000 record
UPC database to find a phone number in their address book.
By the way, PDE has a sophisticated Search Engine within it,
providing structured access to its own databases.
Right now I'm faced with two alternatives:
A) Implement a C language file scan that will work with Find,
and then provide a configuration option to allow users to
disable this, with a very strong recommendation that it always
be disabled! In other words, spend a lot of effort to add
a feature to meet Platinum requirements that will normally be
suppressed.
We'd also have to modify the C++ classes to leave information
to coordinate with the C language file scan. And this whole
exercise would be a validation nightmare.
B) Obtain an official exception for non-support of Find because of
(i) the C++ issue (not our fault!) and
(ii) the negative User effect of Find hitting these large databases.
Does anyone have any relevant experience with this problem?
Has anyone received exceptions for Find support for similar reasons?
Roger Stringer
Marietta Systems, Inc.
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/