Devart Forums

Please use this guidance:
http://www.devart.com/mysqlnet/faq.html#q38

We have fixed the problem with UniCode parameters.
Look forward for the next build.

P.S. Oracle variables must be quoted.

To compile an application that uses OraDirect .NET components, you have to install OraDirect .NET on your machine (it automatically registers our assemblies in GAC).
To run the application on end-user machine it is enough to have our assemblies in the application's directory.
More: http://www.devart.com/oranet/faq.html#q12

Please specify the line where OverflowException arises.

We are investigating this problem.
You will be notified on results as soon as possible.

PostgreSQLDirect .NET Mobile Edition supports such functionality.
You can freely download Trial Edition of this Devart product here: http://www.devart.com/pgsqlnet/download.html
When you install it you will find the project samples (C# and VB) in Start Menu or in the installation folder.

Please provide us detailed information about the error and what steps we should follow to reproduce it.

Applications seek assemblies to load in GAC firstly, then in the bin directory.
If you specified needed version in project's references, it will be loaded. Please make sure there are no policy.*.CoreLab.Data and policy.*.CoreLab.Oracle in your GAC.
If your application loads assemblies of versions specified in *.config files you just need to change these files.

Oracle client x64 can be installed just in another home folder.

According to the stack trace OverflowException is probably caused by BasesDeDatos.BaseDeDatos.ProcAlmacExecute(String sStoredProcedure, ListaParamsBD& ListaParametros, TransaccionBD& oTrans).
Please make sure this exception is caused by our components. If it is really an error of our product, provide us with sample project or some lines of code that we can use to reproduce the error.

New build of OraDirect .NET version 4.75.40 is available!
More: http://devart.com/forums/viewtopic.php?t=12756

Please make sure you are using Oracle client that supports x64 mode. OraDirect .NET 4.70 should work at x64 Windows 2003 Server correctly and deploy in IIS without problems.

Please specify more clearly the problem. Give us a sample so we can reproduce the error.
Maybe you will find it useful: http://devart.com/mysqlnet/docs/
Also you may take advantage of using an additional tool called DBMonitor to extend monitoring capabilities of our data access product: http://www.devart.com/dbmonitor/

Try to set Pooling=false in the connection string. It can be a connection pooling problem. See more: http://www.devart.com/oranet/faq.html#q53

We have fixed the DataSet Wizard problem for MyDirect .NET.

Look forward for the next build.