|
Hi,
I would like to know how to read, modify and write an Excel file in a Windows form.
Does anyone has any experience and sample code?
I am using Visual Basic 2017.
Thanks!
Frank
modified 22-Feb-18 9:01am.
|
|
|
|
|
There are the Microsoft.Office.Interop libraries for interacting with Office products, and lots of sample code on the net if you google it. Here[^] tells you how to add the Excel one to your project.
Note though that this is only a workable solution for Winforms - if you're writing Webforms, you'll need a third-party solution (which may be easier to work with anyway, if you or whoever you're working for can afford it - they're generally not cheap.)
|
|
|
|
|
Thanks for your info!
I will look into it.
Frank
|
|
|
|
|
Syncfusion provides a set of non-UI tools for this purpose. They have a Community version if you don't wish to spend thousands of dollars for the commercial version. You can create, read and write Excel and Word files and integrate it into a WinForms or WPF application. Bit of a learning curve, but it's a fairly powerful set of tools. Thorough documentation and responsive live help even with the free version. There also are 3 grid controls included if you wish to build your own Excel clone.
Syncfusion XlsIO[^]
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Hello !
I'm using vb.net 2013
Is there any way to open a form full screen? ( I mean the same effect that I can have on youtube when choose to play full screen , or in games that can show full screen ) ?
Thank you !
|
|
|
|
|
Sure, open a form with a windowstate of WS_MAXIMIZED and make it borderless. If you want to improve on youtube, you open your own desktop-object 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hello !
I'm using vb.net 2013 , sql server 2008 R2.
I'm using SMO to backup and restore databases.
The problem is that this working only on SQL server 2008R2.
If I try my application with other Sql server versions it doesn't work.
Is there any way to make it work with all sql server versions ?
Thank you !
|
|
|
|
|
Different versions of Sql Server have their own respective SMO, as it is bound to the capabilities of that version. To "make it work" with all versions, you'd have to make a facade that loads the correct version of SMO and manipulates the target for you.
Still doesn't mean that you can restore a 2012 database on a 2008 server, so limits as described on MSDN still apply.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
And there is another way to do that , I mean without SMO ?
|
|
|
|
|
Issue Sql-commands for what you want to achieve; the backup-command is supported by most versions of SQL Server.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I've read somewhere that if I use SMO files from the latest SQL server version , these can work with lower versions too.
Is this true ?
|
|
|
|
|
Yes
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hello !
I'm using vb.net 2013 , SQL server 2008 R2 and entity Frameowrk 6.
I have a situation where on the database , I need to have a foreign key refer the primary key on the same Table.
Employe Table
------------
ID
Name
Position
Manager ID
ID is the primary key , Manager ID is the foreign key , and as the manager is also an employee on the same table , this foreign key refer to the primary key ID on the table employee. But several employees can have the same Manager ID.
I want to know if this is possible and safe to use on sql server and also to work with it on Entity Framework.
Thank you !
|
|
|
|
|
desanti wrote:
I want to know if this is possible and safe to use on sql server and also to work with it on Entity Framework.
That's a rather common thing to do. Without knowing much EF, I'm going to say that it is possible and safe.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
A structure known as a pig's ear!
Recursive Relationships
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Hello !
On Visual studio 2017 , is there possible to use Entity framework 6 , with Database first ?
Because i can't find a way to start a such project.
Thank you !
|
|
|
|
|
Google for "entity framework 6 database first tutorial". The version of Visual Studio does not matter.
Before you dive into a project using EF, Google for "entity framework database first vs code first", to understand what the differences and restrictions on what you can do are going to be for each method.
|
|
|
|
|
Thank you !
I know how to use and work with Entity framework and EF6 with database first.
I want to use it as I've used on Visual studio 2013.
But on Visual studio 2017 , I can't find a way how to start a project with EF6 and Database first.
It seems that VS 2017 is using only Entity framework Core and dropped the support for EF6 ? Or i'm wrong ?
|
|
|
|
|
Sigh ... A little Google goes a long way.
Right-click your project, pick Add --> New Item. Click on Data in the left pane. Double-click ADO.NET Entity Data Model. Follow the wizard.
|
|
|
|
|
desanti wrote: It seems that VS 2017 is using only Entity framework Core and dropped the support for EF6 ? Or i'm wrong ?
You're wrong. I'm using EF6 (not Core) in VS2017, and it's supported perfectly well. You just need to add a reference to the NuGet package called "EntityFramework".
(EF Core is "the future", and will receive the bulk of Microsoft's attention from now on. But there are still a few things that it doesn't support.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: EF Core is "the future", and will receive the bulk of Microsoft's attention from now on
Yeah, there's an upgrade I'm not looking forward to. Hopefully we don't have a ton of work to do on a web app that we spent two years writing, using EF 6.x.
Richard Deeming wrote: ut there are still a few things that it doesn't support
...and there's the reason we haven't dug into it yet.
|
|
|
|
|
And you just know that two months after upgrading, Microsoft will announce that it's being replaced with a newer, shinier version, and the version you've just upgraded to is no longer being maintained. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Man, you speak the truth!
When we started the project it was a about a month before 6.0 came out, so we reworked from 5 to 6.0, then migrations to every 6.x version there is.
Don't get me started on MVC.
|
|
|
|
|
Richard Deeming wrote: (EF Core is "the future", and will receive the bulk of Microsoft's attention from now on. But there are still a few things that it doesn't support.)
Right up until they DEPRECATE the bloody thing and come up with some new insanity for us to work with.
AAAAAaaaahhhhhhhhhhhhhhhh pft!
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
