Hello,
we use the Map Connections Dialog to query and post Oracle data from a configured graphical source.
The workflow looks like: query data > lock for edit > edit > post back.
Since there are cases where we need to edit a bunch of datasets (like 200k+) it takes a long time to query data (particularly when using a fence from a polygon) and much more time to lock these datasets (like more than an hour) until it comes to the real work.
In order to improve the workflow we configured all the where-clauses we need and stored that as an ORAX-file. That works but not with the valid date. For each feature it has the date from ORAX-file-creation stored and when I reload this ORAX-template it shows up the old date but we want to query current state datasets. Is there a way to get that improved, I couldn't find a VBA-based option to operate with Map Connections explorer. I could alter the old date to be current manually but we've got a bunch of features to query and that would take a while.
A second question is whether I may alter the locking type from pessimistic to optimistic (that is greyed out for some reasons) without using the Oracle versioning option. It takes much longer creating a new Oracle version and querying/posting data that way. I know there are data security issues with concurrent data edition but that's not the case here.
Kind Regards,
Maik
Maik, regarding the first question about the Orax file and making the Where clause more dynamically. For a user I made a VBA with a form where the user enters a search value. The Orax file is updated and the spatial query is executed with a keyin. In this way the user can quickly modify the Where clause in a spatial query without using the Edit Where Clause dialog.. This example can be modified to change the date to the actual data in the Orax files.
Hello Kees,
that VBA would help us managing the where clauses. I figured out that we may alter the valid date in one go when changing the date for the datasource (not for each feature). That will update the date value for each feature.
Editing the ORAX-file manually I could alter the pessimistic option from true to false but that seams to be the dirty way.
Is your VBA available somewhere?
Hi Maik, I will anonymize the VBA first and check the documentation. I will upload this soon.