I dont think that cmd.DeriveParameters is a valid statement in vb.net, at least not for an OdbcCommand. I thought about the try-catch, just reports the same error, "Syntax Error". I really hate FoxPro... And now, adding color, a group of anonymous Latin American meat packing glitterati

Yes, the grid is bound at runtime, so although I know what the columns will be for the most part, they could change.

Got a solution if anyone is interested: In order to do this, you will need to call the GetFirstColumn method on the Columns collection, as this method will take display order into account (while the iterator will not). You need to follow that up with a call to GetNextColumn using the previous column. This makes it perfect for an iterator: private static IEnumerableGetDisplayOrderEnumeration(DataGridViewColumnCollection columns) { // Get the first column. DataGridViewColumn column = columns.GetFirstColumn(DataGridViewElementStates.None); // Continue while there is a column. while (column != null) { // Yield the column. yield return column; // Get the next column. column = columns.GetNextColumn(column,DataGridViewElementStates.None, DataGridViewElementStates.None); } } The yield keyword will help create an IEnumerable implementation which you can use a foreach statement to cycle though. You can use it to get the name of the column to get the value of from the row: for (int r = 0; r <= dgvMain.Rows.Count - 2; r++) { foreach (DataGridViewColumn c in GetDisplayOrderEnumeration(dgvMain.Columns)) { value = dgvMain.Rows[r].Cells[c.Name].Value.ToString(); } } The method I gave you will give you an enumeration you can cycle through to get the rows in the display order, which you can then use to access the values in the same order in the underlying data source. Thanks to Nicholas over at the msdn forums.

"take a look to xws.NewLineOnAttributes = True" Thanks, that was stupidity on my part. So I'm stuck with utf-16 unless I switch away from a string builder/writer. Thanks for the help.

Matt Sollars has wrote two articles on the subject WebPageSecurity[^] and WebPageSecurity_v2[^]. I've appled this code and it's outstanding.

Try using a Module. Extreme Exe

Yes. Dave Kreskowiak Microsoft MVP - Visual Basic

No, the application won't error out because what you're *really* done is create a new .NET wrapper dll around the COM dll. Your application will be distributed with the .NET wrapper dll, and your application will function fine. However, if you call into the .NET wrapper dll, which in turn tries to call into the COM dll, then that function call will fail with an exception. Tech, life, family, faith: Give me a visit. I'm currently blogging about: For Christians: The Significance of Yom Teruah The apostle Paul, modernly speaking: Epistles of Paul Judah Himango