Page 1 of 1
oldValue
Posted: Fri 24 Jun 2005 18:39
by lz
I Get this error when I hit the Generate Commands button
ArgumentNullException: Value cannot be null. Parameter name: oldValue
What might I be doing wrong?
thanks
oldValue
Posted: Fri 24 Jun 2005 19:48
by lz
O and when i call update from the dataadapter i get the same error
oldValue
Posted: Sat 25 Jun 2005 12:08
by al
I am also getting this error. Any help would be appreciated.
Re: oldValue
Posted: Mon 27 Jun 2005 07:06
by Serious
lz wrote:O and when i call update from the dataadapter i get the same error
Does this problem occur only in design-time? If so, please describe in details what you do and what is the behavior of the DataAdapter designer. Include MySQLDirect .NET version in your message.
Re: oldValue
Posted: Mon 27 Jun 2005 13:41
by al
I don't know about lz, but in my situation:
I have the MySQL server explorer open.
Step 1: I drag a table from the server explorer onto the form. This creates a MySQLConnection and MySQLDataAdapter component, and a "SELECT * FROM " query.
Step 2: Right click on MySQLDataAdapter component and select "Configure Data Adpater..."
Step 3: Go to Command Generator tab and click generate commands. An error will occur that states:
The following exception has occured:
ArgumentNullException: Value cannot be null.
Parameter name: oldValue
In my situation, this only occurs in design time. I am using:
Visual Studio .NET 2003 7.1.3088
.NET Framework 1.1.4322 sp1
CoreLab.MySql 2.80.7.0
Hope this helps.
Andy
re: oldValue
Posted: Mon 27 Jun 2005 13:46
by al
One more thing... This behavior was not occuring with the trial version. It was after I installed the mysqlnet280pro.msi that this started occuring.
Thanks, Andy
Posted: Wed 29 Jun 2005 07:10
by Serious
We have fixed this problem for the MySQLDirect .NET.
Look forward for the next build.
old value
Posted: Tue 05 Jul 2005 13:39
by sa
it doesn't still seem to work. could you elaborate further on how to make it work
so what is the answer with the current version I just bought
Posted: Wed 06 Jul 2005 13:48
by bdalton
so what is the answer with the current version I just bought??
Posted: Mon 11 Jul 2005 11:48
by Serious
New build will be released on this week. We have fixed this bug in this version.