Hi Paul,

I am sorry it took so long to get back to you. I have working with your Custom Data Access C# example for free fpw26 tables. You are amazing. I struggled for so long and then, pop, you simply post a complete solution on an open forum. All of us attempting to bridge the gap between the old and new technology owe you ton of gratitude.

When I received your code I read it through and saw that you were using an old Fox table with 10 fields ( 9 Character, 1 Integer). I modified one of my tables to have 10 fields and did a simple cut and paste. My modified table worked with the mm.net framework just as you stated it would. Then I sat back and I remembered that I have at least 25 additional tables that need custom data access classes.

I created a Data Access Class Wizard (actually a poor man’s version because there is no UI yet) in vfp8. Now I have 25 custom data access classes that all work with the mm.net framework.

In closing I am reminded of a technology story I heard in college 30 years ago. An American company sent a Japanese company, which they were collaborating with, a copper wire the size of a human hair. Two weeks later the Japanese company sent the hair back split in two (length wise). I’m not saying that I split your hair in two but it was a great story don’t you think. If you want my vfp code please do not hesitate to ask for it.

Regards,
Neil




>>But what length?
>>
>
>The .NET docs say that: "For variable-length data types, Size describes the maximum amount of data to transmit to the server. For example, for a Unicode string value, Size could be used to limit the amount of data sent to the server to the first one hundred characters."
>
>I don't know if you could set this value to "0" to have it send any length of data you'd like. Try it and let us know ;-) If not, I'd probably just set this to some large value, where I'm sure I'm not going to run into a limitation w/my memo fields.