tranchemontaigne
Registered User.
- Local time
- Today, 03:43
- Joined
- Aug 12, 2008
- Messages
- 203
I have a block of VBA code that provides search functionality within an MS Access 2000 database. The end user needs to query a linked Oracle data table that I cannot access. I was able to create link to the Oracle 11g table, then copy the table structure and data to a local MS Access table for development purposes. At my desk and at the end user's desk we can get the search function to run perfectly when creating and running a simple query against the local MS Access table. When the same code block is run against the linked Oracle table it fails without catching an error.
Though I'm not sure if this is relevant, the search function does employ wild cards and uses them to define the results recordset. As you would expect, within the VBA code I am using percentage signs (%) for wild card characters. This decision was made because I have never been able to get the MS Access engine to create a recordset through VBA code using an asterisk (*) character. Attempting to define a recordset in VBA using an asterisk (*) as a wild card character in a SQL statement has always failed for me without generating an error.
Has anyone any tips for resolving this problem? So long as I'm unable to directly test any calls to Oracle, I want to make sure that I have thoroughly investigated solutions before I attempt to deliver an untested fix.
NOTE: Though I am physicaly located in the same complex as the customer and authorized to view the contents of the Oracle table, I am not able to receive permissions to connect to the actual data store, and am also prevented from creating a local Oracle Express instance.
Though I'm not sure if this is relevant, the search function does employ wild cards and uses them to define the results recordset. As you would expect, within the VBA code I am using percentage signs (%) for wild card characters. This decision was made because I have never been able to get the MS Access engine to create a recordset through VBA code using an asterisk (*) character. Attempting to define a recordset in VBA using an asterisk (*) as a wild card character in a SQL statement has always failed for me without generating an error.
Has anyone any tips for resolving this problem? So long as I'm unable to directly test any calls to Oracle, I want to make sure that I have thoroughly investigated solutions before I attempt to deliver an untested fix.
NOTE: Though I am physicaly located in the same complex as the customer and authorized to view the contents of the Oracle table, I am not able to receive permissions to connect to the actual data store, and am also prevented from creating a local Oracle Express instance.