Devart Forums

Could you please try MyDirect .NET v.3.55.25?
If the problem is still there please send me (alexeyman*crlab*com) a small test project to reproduce the problem.
It is desirable to use 'test' schema objects, otherwise
include the definition of your own database objects.
If it is impossible for you to create the test project, send
us a piece of your code where the error occurs or describe steps to
reproduce the problem.

You can fix the mentioned bug in the old version of OraDirect .NET and EF beta 3 by opening an Oracle connection in the Server Explorer.
But please note EF beta 3 is not compatible with latest EF updates.

Hello,

Generally speaking, WPF itself has quite poor design-time data access support.
There should be no problem with using MyDirect .NET DataSet wizard though.
Do you experience any difficulties with it?

Regards,
Alexey.

Hello Cyrille,

Unfortunately, MyDirect .NET doesn't support distributed transactions now.
Probably, it will support them in future.
No time frame is available at this moment.

Regards,
Alexey.

Hello Manuel,

Try setting the Modifiers property of the DataSet instance on the form (e.g. DataSet1)
to public. This should solve the problem.

Regards,
Alexey.

Hello,

Please see my reply here:
http://crlab.com/forums/viewtopic.php?t=12334

Regards,
Alexey.

Hello again,

This was a bug of Microsoft EDM wizard that has already been solved in the mentioned updates.
You should uninstall EF beta 3 and EF Tools beta 3 and install the new updates.

Regards,
Alexey.

Hello,

Do you have Visual Studio 2008 SP 1 beta and .NET Framework 3.5 SP 1 beta installed?

Regards,
Alexey.

Hello,

Please send me (alexeyman*crlab*com) a small test project to
reproduce the problem.
It is desirable to use 'test' schema objects, otherwise
include the definition of your own database objects.
If it is impossible for you to create the test project, send
us a piece of your code where the error occurs or describe steps to
reproduce the problem.
What is the version/edition of the product you use?

Regards,
Alexey.

Hello,

This bug with negative timestamp has been already fixed in the newest build.
But we found another related issue.
If the negative timespan contains minutes it's not parsed correctly. The problem is fixed already.
Look forward to the next build.

Regards,
Alexey.

Please send me (alexeyman*crlab*com) a small test project to
reproduce the problem.
It is desirable to use 'test' schema objects, otherwise
include the definition of your own database objects.
If it is impossible for you to create the test project, send
us a piece of your code where the error occurs.

1) What is the version/edition of the product you use?
2) What exception do you get?

Hello,

XMLTYPE will be supported in the next build of OraDirect .NET,
so you will be able to perform the mentioned actions.
Estimated time for the release is two weeks.

Regrads,
Alexey.

Most likely using separate connections in different threads will solve the problem.
You can try running the application in debug mode and see where it throws the exception and what threads were running.
Presumably, as soon as you get the call stack and the error message you will find the source of the problem.
Please let me know on the results.

Hello,

Well, MySqlDependency will fire an event anyway.
It doesn't matter what data you have got in the local client memory.
MySqlDependency always compares hashes for the table on server side.
Say, I have a table tbl1 with rows:
1)AAA AAA
2)BBB BBB
3)CCC CCC
This is a table on the server.
Also I have a user-client U1.
U1 loads tbl1 to the his machine's managed heap.
Every 5 seconds MySqlDependency from U1 application calculates a hash for the tbl1 (that is stored on the server). Say the hash value is:
_currentHash = “ABC”
U1 locally changes the tbl1:
1) AAA BBB
2) BBB CCC
3) CCC DDD

MySqlDependency compares _currentHash (which is “ABC” now) to the new hash, which is also “ABC”, as tbl1 on the server has not changed. The event is not fired.
Then U1 updates tbl1 and overrides the data on the server side.

Next time MySqlDependency calculates a hash for the tbl1 and gets a new hash value, say:
_newHash = “AAA”. Finally, MySqlDependency compares “AAA” (_newHash) and “ABC” (_currentHash) and fires an event.

Regards,
Alexey.

Hello Dave,

1) No, this is not correct.
On the first internal query MySqlDependency calculates a small unique hash value for the table.
With the next queries MySqlDependency recalculates the table's hash and compares the newer value with the older one.
If they do not match, the table has been changed.
So it doesn't matter who has updated the table. MySqlDependency is responsible for tracking any change in the table.

2) Basically, yes.
But usually you don't want to show all data from the table to the user.
Instead you would rather sort it, limit the rows amount, say to the first hundred rows or perform asynchronous queries.
You can find some samples in the “Asynchronous Query Execution” topic in the product help.

Regards,
Alexey.