How do I contact regarding weird problems, are there any Microsoftpeople looking?

  • Thread starter Thread starter Christian Westerlund
  • Start date Start date
C

Christian Westerlund

Hi!

I seem to run into weird problems and when I post info about them on
this and other microsoft newsgroups I usually don't get any replies.

Recently I posted about a problem I got when i filled a dataset with
data from a text-file. From this post: (Fill a dataset causes an
E_UNEXPECTED 0x8000FFFF) exception)
I got the following exception:
E_UNEXPECTED (0x8000FFFF)

So, my question is the following:

Are there any microsoft people looking through this newsgroup?
Are there any other places I should be posting my "weird" problems?

Christian
 
Christian,

The problem you are having is probably not in the purview of ADO.NET, it is
probably being generated by the underlying odbc/oledb layer that ado.net is
using.
Do you have an alternate non .net way of accessing the data in a similar
fashion?

Secondly, you mention that you are using ado.net to read data from text
files - any reason you are not using System.IO for this? Also, you could
write your own completely managed .net data provider to read to/from text
files.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
 
Hi!

The reason I'm using ado.net is that the possibilites are endless. The
ability to execute SQL-statements on a text file is one huge reason. It
would require a lot more coding if I should use System.IO to do that.
I haven't looked into building a .net data provider, maybe that could be
an option but to me it seems that I would have to use System.IO here and
implement a lot of interfaces and the provider has to support SQL. Doing
all this when there is an existing provider that should be doing all this.
Using an existing .net data provider is still the best option, I wonder
why the provider is having problem reading long column data.

Christian
 
I wonder why the provider is having problem reading long column data

Couldn't say .. but I will tell you this much that .. the error you mention
is reminiscent of a COM error, it is probably coming from the OLEDB layer.
The usual translation in VB6 friendly language used to be "An unknown error
was generated from an unknown source" -- which sucks, but then COM sucked in
comparison to .NET anyway. Even then, the error was not completely
indiagnosable, but I suspect there just might be a better way of grabbing
your nose in this case.

What exactly are you trying to do, I understand ADO.NET possibilities are
limitless, but if you wouldn't mind mentioning your exact purpose/goal I
might be able to come up with a better solution.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
 
Well, I have files with data.
The data is saved from vb6 types directly down to file.
I don't know how or when the data is saved.

I want to read these files from .NET.
There can be many different types and therefor many files which I would
have to read.
My solutions top priority would be speed of execution. I'm also aiming
for a dynamic solution because of the many different files.
That's why I was going for ADO.NET.

I appreciate all your help Sahil Malik.

Christian
 
Back
Top