FZelle

Normaly you would use ADOX for this task, but since vista there is a problem with "just" adding that COM component, because vista has a version 6.0 of the mdac. But you can use this to get your goal: object ADOXCat = Activator.CreateInstance(Type.GetTypeFromProgID("ADOX.Catalog")); ADOXCat.GetType().InvokeMember("Create", System.Reflection.BindingFlags.InvokeMethod, null, ADOXCat, new string[] { ConnectionString });

You will always run into this problem, if you don't understand the problem. In FW 1.1 it was possible, but not advisable, to call the UI-Thread from the workerthread. In FW 2.0 this is not allowed anymore. You always have to invoke everything from the workerthread. If you only do easy things look at the backgroundworker. Otherwise look into Invoking.

How are the Temp-Path settings on that one computer

In FW 2.0 they are also part of the DataTable.

No you don't neet to create DataRows. dataG.Rows[0]["Name"] has the value of the "Name" column in the first datarow

That's because you've got the mdb in your solution and that one gets copied to the bin dir everytime you start in the IDE. Youz can change the properties of the file to "copy never".

If you are useing the Database in Filemode, and you have the MDF in your project, than the file gets copied everytime you start the software, so all changes are overwritten.

The Table in DataView is the unfiltered Table. So you are not looping through the filtered values. Easier for your purpose would be the DataTable.Select() funktion.

http://www.c-sharpcorner.com/Code/2004/Feb/ODP.NET02.asp Here you have everything needed for ODP. You are sure your Servername is correct?

And why don't you use the order you want to use ( orderXmlItem )? You always use the rootnode ( order) !

To create a new column in the DataBase you can't use this way. You have to use a normal SQL-Command like "ALTER TABLE ADD COLUMNNAME COLTYPE".

This shouldn't work as expected. You are ignoring the view with oDataView.Table.Rows. You have to use oDataView = oDataTable.DefaultView For Each lo_node In lo_nodeSet.SelectNodes("attachments") lo_attachments = GetDataElement(lo_node, "attachments") ls_name = lo_attachments.GetAttribute("KeyName") oDataView.RowFileter = "name = '" & ls_name & "'" 'some code For Each oDataRowView In oDataView 'some code Next 'more code Next

Just a question, why do you use a Provider that actually ignores ADO.NET and insists on it's own methods? If you would use http://sourceforge.net/projects/adodotnetsqlite/ for a FW 1.1 prg and http://sourceforge.net/projects/sqlite-dotnet2/ for a FW 2.0 program you could use the std. mechanisms in ADO.NET.

Put Try/Catch around your DB-Code, than you get the real Problem in the Statement. Maybee some Parameters are to long, spelled incorrect ...

You need the "new" Sql-Server express. The old one didn't have Fulltextsearch. With that Update you also get Reportingservices and the Managment Studio