Sharing the goodness…
Beth Massi is a Senior Program Manager on the Visual Studio team at Microsoft and a community champion for business application developers. Learn more about Beth.
More videos »
One really handy thing to do with relational data is to import and export it to Excel. This can be a total snap using LINQ to XML in Visual Basic 2008. For example, let's say I want to import data from an Excel spreadsheet into a local database file like SQL Compact Edition. I also want to be able to export that data back into an Excel spreadsheet, basically allowing me to edit the data from either my application or Excel.
The trick really is getting the format of the Excel spreadsheet as XML and using that sheet as a template to populate your data. First open Excel (for this example I'll use the Excel 2003 format so you can use Excel 2007 or 2003 to follow along). Next let's enter some column headers, for my example I have a list of customers I want to import/export so the fields I'll want are Abbrev, Name, Phone, Country. It's also helpful to enter one line of dummy data (you'll see why in a second). So here' what we've got:
Now what I want to do is get all the customers stored in my little SQL CE local database into this spreadsheet.
(As a side note, you can easily add a SQL CE local database file to your project by selecting the "Local Database" new item template in Visual Studio 2008. You can easily access the data in SQL CE sdf files by adding a new datasource (Data --> Add New Datasource), adding a new connection, and change the data source to "Microsoft Compact SQL Server 3.5" then locate or create the .sdf file. Then you can create typed Datasets like normal.)
So I have a form where I just dragged my CustomersDataSet that I created from my local database file onto it as a DataGridView. This also sets up the BindingSource and BindingNavigator toolstrip like we'd expect. I added a couple buttons to the toolstrip one called "Import" and one called "Export".
Now in order to get the Excel spreadsheet into an XML format you can simply "Save As.." and select "XML Spreadsheet 2003 (.xml)" as the file type. Now navigate to that file and open it with notepad, select and copy all the text into your clipboard. Open up your Visual Basic program, type "Dim sheet =" and then paste the contents of your clipboard directly into the editor. It should look something like this (I collapsed some of the sections we're going to ignore):
Next we need to import the namespaces in the spreadsheet. This is necessary so that when we create and query our XML, Visual Basic will know the correct namespaces we're working with. So at the top of code file for our form we'll add:
Imports <xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet">Imports <xmlns:html="http://www.w3.org/TR/REC-html40">
Now we can write a query that will take all of the customers in our SQL CE database file (technically the typed DataSet that was created for us) and populate the spreadsheet. You should see your dummy data in the XML above. Cut that out (ctrl-X) because we're going to replace that with all our customers using embedded expressions like so:
Dim customers = _
From customer In Me.CustomersDataSet.Customers _
Where customer.RowState <> DataRowState.Deleted _
AndAlso Not customer.IsAbbrevNull _
Order By customer.Abbrev _
<Cell><Data ss:Type="String"><%= customer.Abbrev %></Data></Cell>
<Cell><Data ss:Type="String"><%= If(customer.IsNameNull, "", customer.Name)%> </Data></Cell>
<Cell><Data ss:Type="String"><%= If(customer.IsPhoneNull, "", customer.Phone)%> </Data></Cell>
<Cell><Data ss:Type="String"><%= If(customer.IsCountryNull, "",customer.Country)%> </Data></Cell>
I'm just selecting the data inside my typed Dataset which is populated in the load of the form, making sure not to grab any deleted rows or rows where the abbreviation is NULL. The customers variable above becomes a collection of XElements (IEnumerable(Of XElement)) and we simply pop that back into the sheet, replacing the dummy line we removed:
<Table ss:ExpandedColumnCount="4" ss:ExpandedRowCount=<%= customers.Count + 1 %> x:FullColumns="1" x:FullRows="1" ss:DefaultRowHeight="15">
<%= customers %>
Also notice that I had to adjust the ss:ExpandedRowCount attribute as well to include the count of our customers plus one for the header row. Now we can write the results out to disk and start Excel:
Okay so now we want to be able to import this data as well. If any rows were added or edited we want that data back in our database. I'm going to use the Abbrev field as the unique identifier of our data. The query we need to write will group join (outer join) the current (non-deleted) rows in our CustomerDataSet to the rows here in the spreadsheet. That way if the resulting items in the collection contain a group (of one CustomerDataRow in this case), then we know that the CustomerDataRow needs to be updated, otherwise we know it's a new customer that needs to be added. We also need to skip the first row because that's our header row in the spreadsheet, and I'm doing an extra check for empty cells.
Dim sheet = XDocument.Load("C:\Customers.xml")
'Skip the first row because that is the header row in the spreadsheet.
'Notice also that we're eliminating deleted rows from the group join.
'We'll use the existence of the group collection to determine if the
' row needs to be added to the database.
Dim customers = From xmlCustomer In sheet...<Row> _
Let Abbrev = xmlCustomer.<Cell>(0) _
Let Name = xmlCustomer.<Cell>(1) _
Let Phone = xmlCustomer.<Cell>(2) _
Let Country = xmlCustomer.<Cell>(3) _
Abbrev IsNot Nothing AndAlso _
Name IsNot Nothing AndAlso _
Phone IsNot Nothing AndAlso _
Country IsNot Nothing _
Group Join customer In _
(From row In Me.CustomersDataSet.Customers _
Where row.RowState <> DataRowState.Deleted _
AndAlso Not row.IsAbbrevNull _
Select row) _
On customer.Abbrev Equals Abbrev _
Into Group _
Abbrev = Abbrev.Value, _
Name = Name.Value, _
Phone = Phone.Value, _
Country = Country.Value, _
'Add or update the customer row depending on if the
' group collection exists.
For Each customer In customers
Dim r As CustomersDataSet.CustomersRow
If customer.Group.Count = 0 Then
'Add new row ands set the customer abbreviation.
' This field is used to determine uniqueness of the data
r = Me.CustomersDataSet.Customers.NewCustomersRow()
r.Abbrev = customer.Abbrev
r = customer.Group(0)
r.Name = customer.Name
r.Phone = customer.Phone
r.Country = customer.Country
If r.RowState = DataRowState.Detached Then
Now we can make changes to the spreadsheet, import the data into our local database, or make changes to our local database and export those changes to Excel. I've attached the complete example built with Visual Basic 2008. You'll also need Excel 2003 or higher to view the spreadsheet. It's worth reiterating that you don't actually need Excel to create the spreadsheet in Visual Basic via code as long as you have the XML format, you just need it if you want to open it in Excel later. Remember we're not using automation, we're just creating XML in a specific format.
i trying to display a data from datagrid to excel sheet using vb6.0 . scenario like below
When i click on command button data from datagrid should display in excel sheet
will some provide code in vb 6.0
I did a project using different data sources based on this article here skydrive.live.com/redir
Wow, I know this post is a bit old but I had a use for this code as I have an application that has an OpenXML implementation (still a bit rough, but works in Prod) for handling Excel work and when I went to play with the code I found a strange behavior. I had a real world Excel spreasheet that had some empty cells.
I only wanted to import a few of the columns and so I set it up using the ordinal reference like:
Let MyField = xmlCustomer.<Cell>(5) _
Let MyNextField = xmlCustomer.<Cell>(6) ...
What I found was that if the cell at column 6 in my original Excel sheet was empty then the xml left it out and the Linq would pull the data from the next non-empty column past the empty one at position 6.
Looking at the xml file itself in a text editor, I see a 'shorthand' that deals with empty cells, like:
<Cell ss:Index="20"><Data ss:Type="Number">0</Data></Cell>
<Cell ss:Index="23"><Data ss:Type="Number">0</Data></Cell>
The syntax ss:Index="20" seems to say 'skip over all the next cells until you get the one at index 20' then get the data from the next two cells, then the next cell that has a value is at index 23 (IOW, skip 22).
Any ideas how I could adjust the LINQ to deal with this ?
I mean short of writing some kind of rule parser myself, which would make this way less elegant and make me want to run back to a 'classic' imp without ever looking back...
Thanks, Beth, in advance.
First of all a big thanks for this article. It really helped me achieve what I needed. However, I cannot see any data in the Excel that gets saved. I checked and made sure that the data existed in the query result but looks like it is not getting saved in Excel. Any thoughts!!!!