-
David, I think I have the installer for the version he is after. (Just located on backup). I can email to you to do with as you wish? curtis
-
Sounds like a problem I've had in the past (though with a different version or Oracle). The 'illegal zero-length' will occur on entity.save if the oracle client is not configured properly. On my install, I had more than one version or Oracle Client, and eventually removed them all and re-installed. (When I say removed, I mean I uninstalled and also
-
Thank you sir... Sounds like a perfect solution to me.
-
As noted by several posts, options Ignore Schema and Ignore Catalog must be unchecked to work with Oracle (2009.1.0209.0). This works perfectly provided the generated code accesses the schema from which it was generated. If, however, I create a duplicate schema (for a testing environment) I can't simply change the connection string. I must re-generate
-
What's the chances that this is an overloaded procedure? Microsoft's System.Data.OracleClient (which is what ES uses) doesn't play well with overloaded procedures. Just a thought.
-
I'm having a similar problem. An application works fine on production and my dev machine. The IIS test machine returns this same error. The only difference I find is the version of System.Data.OracleClient is newer on the test machine (2.0.50727.3082, presumably installed with Net 2.0 SP2). The version on the dev machine is (2.0.50727.1433) and I'm
-
Looks to me like your custom load is only returning the Address_id.
-
You're welcome. I've received much help from these forums, so I'm just passing it on. http://www.codeproject.com/KB/database/OracleSPWrapper.aspx Is what I started with. It uses the Microsoft provider (which accesses the installed Oracle Client) to make the Package Calls. This will work fine provided you have no overloaded procedures. It lacks a strongly
-
I am willing to provide you with the two projects that I use to generate code to call procedures in Oracle Packages. (But it is a bit of a hack) The first project was not my original code, but I did improve it a bit (by adding support for overloaded procedures and changing the provider to Oracle from Microsoft). That generated a class to call each particular
-
I can think of two issues with supporting package calls in Oracle fully -Overloaded Procedures I can only give specifics for our environment, but with Oracle Client 10g client installed, the Microsoft provider ( .NET 2.0) can not properly distinguish between type and number of parameters between the different overloaded procedures. I had to abandon