|
IIRC there are about 5 different ways of opening a sheet/book/etc. You need to find some samples and work out which method you need. This generally takes a load of reaserch into articles and samples etc.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I dunno, I use ADO.net and the OleDb connector to read and write Excel and I don't think it will do everything you want.
|
|
|
|
|
Yes I do too,using ADO.net and the OleDb connector to read and write,so this is not possible with ado.net
|
|
|
|
|
Hello,
I'm trying to write a UI in C# for an existing Access database.
1.I've connected to Northwind sample database according to MSDN tutorial:
http://msdn.microsoft.com/en-us/library/ms171893%28VS.80%29.aspx
2.I made a Windows Form Project.
3.I added a button and assigned to it code that modifies an entry in the database.
4.The code for the form looks like this:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
namespace AccessUI
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void button1_Click(object sender, EventArgs e)
{
NwindDataSet.CustomersRow customersRow =
nwindDataSet.Customers.FindByCustomerID("ALFKI");
customersRow.CompanyName = "Updated Company Name";
customersRow.City = "Seattle";
}
}
}
5. Then I run the code, press the button,but after running the code I do not see the changes in the database.
Would you please advice what can be the problem.
Thank you. Polina.
modified on Wednesday, February 23, 2011 5:46 AM
|
|
|
|
|
Member 7697943 wrote: But after running the code I do not see the changes in the database.
Their might be lots of problem. Without seeing your Db update code,
No one can help.
a) You are not even interacting with DB !
b) Query for update is wrong !
etc etc...
download MSDN sample you had mentioned in your post.
try to play/explore with it then imply/mimic the same in your app.
|
|
|
|
|
Without seeing the code which you used to add the new row, it is impossible to guess...
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
|
|
|
|
|
Problem is you are editing record only on UI not in DB.
You have to Update that change in DB. With DataAdapter object you can update that, like
this.TableAdapter.Update(this.NwindDataSet.CustomersRow);
Refer to this for more help.
Hope this help(if yes then please vote )
|
|
|
|
|
i have a textbox in form1,
i want send the information of textbox to combobox in form2 ???
how i can???
help me please
modified on Saturday, February 26, 2011 4:26 PM
|
|
|
|
|
Read This. It will help !
And is correct approach.
Other approach (if small interaction is involved)
form2 obj = new form2(textBox.text);
obj.Show();
public form2(string text)
{
InitializeComponent();
combobox.Items.Add(text);
}
|
|
|
|
|
Thanks!
|
|
|
|
|
hanis29268 wrote: i want send the information of textbox to combobox in form2?
What's wrong with using a simple assignment statement?
I must get a clever new signature for 2011.
|
|
|
|
|
You missed the bit where he said "Form1" and "Form2" then?
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
|
|
|
|
|
No, I just think questions like this are so basic that questioners should be able to work it out for themselves. After all they are just about moving a field or property from one object to another.
I must get a clever new signature for 2011.
|
|
|
|
|
I know what you mean, but the concept of private vs public does seem to confuse beginners: perhaps it should be introduced earlier in the courses? Along with decent naming, commenting, what an instance is, why not to use static, etc. , etc., etc.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
|
|
|
|
|
Hi
I'm using the WIA Library 2.0 from the Microsoft website to scan multiple pages. I then convert these scanned images to byte arrays and keep them in a List<byte[]>. My next goal is to combine these images/byte arrays and save it as 1 single file. I would prefer saving it as PDF, but TIFF will also do for multiple pages. I had a look at the Codeproject article on how to use the Ghostscript API, but I`m looking for a simpler way.. preferably without using third-party tools.
Any hints would be appreciated
Thanks
|
|
|
|
|
I came across this the other day while trying to convert Byte Arrays stored in a database back into Tiff files. Create Tiff Image Page By Page[^] Maybe it could help you.
Happy coding.
|
|
|
|
|
|
Great link, thanks.
|
|
|
|
|
Nice Link it help me also
|
|
|
|
|
Would anyone care to point out to me what the main differences between SqlDataReader and SqlDataAdapter are, when to use one and when to use the other?
I've been using SqlDataReader exclusively so far and have not yet even bothered to read what SqlDataAdapter really is about.
|
|
|
|
|
The big difference is time.
When you use a SqlDataReader, you open a connection, start reading, then loop though each record, processing it. When you have finished, you close the database connection.
When you use a SqlDataAdapter, it opens the connection, takes a snapshot of the database, and closes the connection. You can then process the records.
You can use a DataAdapter to bind a data source to a control, such as a DataGridView, rather than iterating though each record.
Have a look on Google: "SqlDataReader vs. SqlDataAdapter" will give you a lot of hits, most of which are pretty useful.
(And yes, I do know that a SqlDataAdapter leaves the connection open if it was already - that's the advanced course, ok?)
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
|
|
|
|
|
OK thanks, that helps. As regards databinding, I've always used SqlDataReader , even for that, like so:
using (SqlDataReader mySqlDataReader = mySqlCommand.ExecuteReader())
{
DataSet myDataSet = new DataSet();
DataTable myDataTable = new DataTable();
myDataSet.Tables.Add(myDataTable);
myDataSet.Load(mySqlDataReader, LoadOption.PreserveChanges, myDataSource.Tables[0]);
myDataGridView.DataSource = myDataSource.Tables[0];
}
Do you know of any advantage over this by rather using a SqlDataAdapter ? How would you do that?
|
|
|
|
|
I wouldn't even use a DataSet like that, I define and fill DataTables myself. This[^] article shows how.
|
|
|
|
|
Thanks, it looks interesting, but jeeeez, it looks complicated. I'll go through it more attentively when I have a little more time but, briefly, could you explain why that method is better than using a DataSet like in my earlier example?
|
|
|
|
|
I personally like to stick to DataReaders and convert the data into proper CLR objects, rather than binding directly to a DataAdapter. Especially when it comes to WPF applications, as then you can have all the proper interfaces such as IDataErrorInfo and INotifyPropertyChanged which makes Databinding and Validation much easier. I have heard arguments for DataAdapters before but never used them. Just my 2c.
|
|
|
|