| | |
Exporting Data from App To Excel c#
Please support our C# advertiser: Intel Parallel Studio Home
Thread Solved |
•
•
Join Date: Apr 2006
Posts: 88
Reputation:
Solved Threads: 2
Hi,
I am importing data from excel (don't know yet I am going to do that) and export it back into excel. I don't want to have users to import data using excel (due to lack of intelligence) and also it would be faster and more streamline.
I already had a complete app that did it all except I can't get it to run on any other machines. I used office PIA and that is just suck a hassle. I don't want to go down that road again. Now I have been reading posts on how to import data using OLE DB connection and it looks pretty simple.
Now what I am worried about is pushing data back into excel. How does that work? Also I came across a post that said OLD DB isn't for Excel but was originally for Access. Well how ever it falls it anyone could point me in the right directions (Except for Office PIA) I would be grateful.
Thanks!
I am importing data from excel (don't know yet I am going to do that) and export it back into excel. I don't want to have users to import data using excel (due to lack of intelligence) and also it would be faster and more streamline.
I already had a complete app that did it all except I can't get it to run on any other machines. I used office PIA and that is just suck a hassle. I don't want to go down that road again. Now I have been reading posts on how to import data using OLE DB connection and it looks pretty simple.
Now what I am worried about is pushing data back into excel. How does that work? Also I came across a post that said OLD DB isn't for Excel but was originally for Access. Well how ever it falls it anyone could point me in the right directions (Except for Office PIA) I would be grateful.
Thanks!
FYI: OLEDB is for both Excel and Access. Maybe this article will help:
http://support.microsoft.com/default...b;EN-US;257819
Basically, once you start using OLEDB, you can treat the whole deal like it's a database. As such, you'd pull the data out using a SQL SELECT command (that fills a dataset), then you'd edit the data in the dataset, and you'd perform some steps that would Update the contents of the "database".
...That's how the data gets placed back in. Once you start using OLEDB, you can insert rows, update them, delete, etc, just like a SQL database.
That's the most that I could tell you-- I've just started fooling around with ADO DataSets using OLEDB provider for Access. It works great, though. There are whole books on ADO that are available through your favorite tech book retailer-- I suggest you check them out. But for starters, that link I provided might help.
http://support.microsoft.com/default...b;EN-US;257819
Basically, once you start using OLEDB, you can treat the whole deal like it's a database. As such, you'd pull the data out using a SQL SELECT command (that fills a dataset), then you'd edit the data in the dataset, and you'd perform some steps that would Update the contents of the "database".
...That's how the data gets placed back in. Once you start using OLEDB, you can insert rows, update them, delete, etc, just like a SQL database.
That's the most that I could tell you-- I've just started fooling around with ADO DataSets using OLEDB provider for Access. It works great, though. There are whole books on ADO that are available through your favorite tech book retailer-- I suggest you check them out. But for starters, that link I provided might help.
Alex Cavnar, aka alc6379
•
•
Join Date: Apr 2006
Posts: 88
Reputation:
Solved Threads: 2
Thanks A Bunch Man!!!!
•
•
•
•
Originally Posted by alc6379
FYI: OLEDB is for both Excel and Access. Maybe this article will help:
http://support.microsoft.com/default...b;EN-US;257819
Basically, once you start using OLEDB, you can treat the whole deal like it's a database. As such, you'd pull the data out using a SQL SELECT command (that fills a dataset), then you'd edit the data in the dataset, and you'd perform some steps that would Update the contents of the "database".
...That's how the data gets placed back in. Once you start using OLEDB, you can insert rows, update them, delete, etc, just like a SQL database.
That's the most that I could tell you-- I've just started fooling around with ADO DataSets using OLEDB provider for Access. It works great, though. There are whole books on ADO that are available through your favorite tech book retailer-- I suggest you check them out. But for starters, that link I provided might help.
•
•
•
•
Originally Posted by mickwen
Hello,
You can try to use the professional .net component for ms excel.
It support MS Excel , MS Word, HTML , XML , PDF , MS Access ,DBF, SQL Script, SYLK,DIF,CSV ,MS Clipboard format and more.
link removed by moderator
good luck!
Alex Cavnar, aka alc6379
![]() |
Similar Threads
- Export data to Excel Template (MS Access and FileMaker Pro)
- Export from Excel help needed (Mac Software)
- Exporting data into Excel (C)
Other Threads in the C# Forum
- Previous Thread: compare 2 xml files with csharp
- Next Thread: How to connect MS SQL server 2000 with C#
| Thread Tools | Search this Thread |
Tag cloud for C#
.net access algorithm array barchart bitmap box buttons c# chat check checkbox class client color combobox control conversion csharp custom database datagrid datagridview dataset datetime degrees development draganddrop drawing encryption enum event excel file files form format forms function gdi+ httpwebrequest image index input install java label list listbox listener login mandelbrot math mouseclick mysql networking object operator oracle path photoshop picturebox pixelinversion post prime programming radians regex remote remoting resource richtextbox save saving serialization server sleep socket sql statistics stream string table tcp text textbox thread time timer treeview update usercontrol validation view visualstudio webbrowser windows winforms wpf xml






