|
kirankanchinadam wrote: When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Have you fixed this problem? If not, look in the Surface Configuration tool...
If you try to write that in English, I might be able to understand more than a fraction of it. - Guffa
|
|
|
|
|
i want to connect vb.net to sql server 2000 how to connect
|
|
|
|
|
Rmesh wrote: i want to connect vb.net to sql server 2000 how to connect
Use a connection string, here is a useful site: http://www.connectionstrings.com[^]
Some people have a memory and an attention span, you should try them out one day. - Jeremy Falcon
|
|
|
|
|
create a SQLConnection object
assign a connection string to the connection object's connection string property
say ConnectionObject.Open();
now u r connected
use this connection object in your command object to run commands in the database
Karam C Bose
|
|
|
|
|
Hi, I have 3 tables, here is the .sql file, just copy and paste starts from the line :
-- STARTS FROM HERE --
DROP TABLE IF EXISTS `gudang_list`;
CREATE TABLE `gudang_list` (
`Gudang ID` varchar(15) character set latin1 NOT NULL default '0',
`Description` varchar(50) character set latin1 NOT NULL default '',
`Address` text character set latin1 NOT NULL,
`Phone 1` varchar(15) character set latin1 NOT NULL default '',
`Manager` varchar(10) character set latin1 NOT NULL default '',
`Maximum Hold` int(5) unsigned NOT NULL default '0',
`Current Hold` int(5) unsigned NOT NULL default '0',
`Created Date` date NOT NULL,
PRIMARY KEY (`Gudang ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
DROP TABLE IF EXISTS `item_general`;
CREATE TABLE `item_general` (
`Item ID` varchar(15) character set latin1 NOT NULL,
`Description` varchar(50) character set latin1 NOT NULL,
`Item Class` varchar(15) character set latin1 NOT NULL default 'Stock Item',
`Active` enum('Yes','No') character set latin1 NOT NULL default 'Yes',
`Subject to Commission` enum('Yes','No') character set latin1 NOT NULL default 'No',
`Description for Sales` text character set latin1,
`Description for Purchases` text character set latin1,
`Price level 1` double(7,2) default NULL,
`Price level 2` double(7,2) default NULL,
`Price level 3` double(7,2) default NULL,
`Price level 4` double(7,2) default NULL,
`Price level 5` double(7,2) default NULL,
`Price level 6` double(7,2) default NULL,
`Price level 7` double(7,2) default NULL,
`Price level 8` double(7,2) default NULL,
`Price level 9` double(7,2) default NULL,
`Price level 10` double(7,2) default NULL,
`Item Tax Type` tinyint(3) unsigned NOT NULL default '1',
`Last Unit Cost` double(7,2) default NULL,
`Cost method` enum('FIFO','LIFO','Average') character set latin1 NOT NULL default 'FIFO',
`GL Sales Account` varchar(15) character set latin1 NOT NULL default '40000',
`GL Inventory Account` varchar(15) character set latin1 NOT NULL default '12000',
`GL Cost of Sales Account` varchar(15) character set latin1 NOT NULL default '50000',
`UPC/SKU` text character set latin1,
`Item Type` varchar(15) character set latin1 default NULL,
`Unit/Measure` varchar(15) character set latin1 default NULL,
`Weight` double(5,2) default NULL,
`Qty on Hand` smallint(5) unsigned default NULL,
`Qty Available` smallint(5) unsigned default NULL,
`Qty on SO's` smallint(5) unsigned default NULL,
`Qty on PO's` smallint(5) unsigned default NULL,
`Qty on Service` smallint(5) unsigned default NULL,
`Minimum Stock` smallint(5) unsigned default NULL,
`Reorder Stock` smallint(5) unsigned default NULL,
`Preferred Vendor ID` varchar(15) character set latin1 default NULL,
`Buyer ID` varchar(15) character set latin1 default NULL,
PRIMARY KEY (`Item ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
DROP TABLE IF EXISTS `item_location`;
CREATE TABLE `item_location` (
`Item ID` varchar(15) collate latin1_general_ci NOT NULL default '',
`Gudang ID` varchar(15) collate latin1_general_ci NOT NULL default '',
`Quantity` smallint(5) unsigned NOT NULL default '0',
PRIMARY KEY (`Item ID`,`Gudang ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
-- ENDS HERE --
I Use MySQL Administrator
When I tried to make a foreign key in table ITEM_LOCATION.
Field "Item ID" will be connected with "Item ID" in table ITEM_GENERAL, with RESTRICT on DELETE and CASCADE on UPDATE.
The problem is, I kept getting this message :
MySQL Error Number 1005
Can't create table 'myDbName\#sql-610-122.frm' (errno 150)
I have another Database with tables like above, but I got no problems when creating foreign key. It's only in the above tables the problem is on.
I just hope it's not a bug...
Any Helps? Thanks.
Enjoy It!
|
|
|
|
|
Tomy1402 wrote: `Item ID` varchar(15) collate latin1_general_ci NOT NULL default '',
Is the underlined part correct? defaults to an empty string?
|
|
|
|
|
Well, I made the tables more simpler:
-- ------------
CREATE DATABASE qwe;
USE qwe;
DROP TABLE IF EXISTS `gudang_list`;
CREATE TABLE `gudang_list` (
`Gudang ID` varchar(15) character set latin1 NOT NULL default 'GA-001',
`Description` varchar(50) character set latin1 NOT NULL default 'Gudang Atas',
PRIMARY KEY (`Gudang ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
DROP TABLE IF EXISTS `item_general`;
CREATE TABLE `item_general` (
`Item ID` varchar(15) character set latin1 NOT NULL default 'KOM-001',
`Description` varchar(50) character set latin1 NOT NULL default 'KOMPUTER',
PRIMARY KEY (`Item ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
DROP TABLE IF EXISTS `item_location`;
CREATE TABLE `item_location` (
`Item ID` varchar(15) collate latin1_general_ci NOT NULL default '',
`Gudang ID` varchar(15) collate latin1_general_ci NOT NULL default '',
PRIMARY KEY (`Item ID`,`Gudang ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;
-- -------------------------
This produces the same error... and I suspect the CHARSET and COLLATE play something about the error..
Just import it using MySQL Administrator.
|
|
|
|
|
Hi again, I changed the CHARSET and COLLATE to utf8 and to utf8_general_ci
It works!
But I just confused how the difference between those CHARSETS and COLLATIONS ?
Enjoy It!
|
|
|
|
|
I am trying to get this program im writing to simply delete a datarow out of the datatable. Here is my code and it doesnt give me any errors it acts like it does it but the data is still there.
Data Tier
Public Sub deleteData(ByVal dIndex As Integer)
Dim row As myDataSet.tblMyRow = Me.tableadapter1.GetData.Row(dIndex)
row.Delete()
Me.myDataSet.AcceptChanges()
End Sub
Business Tier
Public Sub bDeleteData(ByVal bIndex As Integer)
mydataTier.deleteData(bIndex)
End Sub
GUI Tier
Private Sub btnDelete_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnDelete.Click
Dim dIndex As Integer
Dim dCount As Integer
dCount = Me.dataGrid1.SelectedRows.Count
If dCount = 1 Then
dIndex = Me.datagrid1.Rows.GetFirstRow(DataGridViewElementStates.Selected)
myBusTier.bDeleteData(dIndex)
Me.DataSet1.AcceptChanges()
Me.TableAdapter.Fill(Me.DataSet1.myTable)
ElseIf dCount <= 1 Then
MsgBox("Please Select a Row to Delete")
Exit Sub
Else
MsgBox("Please Select One Row at a Time")
Exit Sub
End If
End Sub
Thanx for the ear
Peace
|
|
|
|
|
I have composed a project using MS VC6.0. In this project, I used
CDaoDatabase to connect ACCESS database. it can be compiled without any error or warnning, but when i have it compiled with
MS vc7.0 ,a worning starts to arise:
CDaoDatabase is deprecated....
I don't known how to solve this.
|
|
|
|
|
Yaki_15 wrote: MS vc7.0 ,a worning starts to arise:
CDaoDatabase is deprecated....
I don't known how to solve this.
It is a warning that there is a replacement technology that you should consider using because CDaoDatabase will be getting removed in a future version of MFC.
You may wish to consider reading the current documentation for MFC in the area of databases, it will most likely tell you what should should be migrating towards.
|
|
|
|
|
I'm not sure about CDaoDatabase being removed in a future version of MFC, but I know that DAO is not being ported to 64-bit. That is, I believe the 32-bit runtime is still present for a 32-bit application, but there will be no 64-bit runtime. As such, CDaoDatabase will no longer work if you recompile your application for 64-bit.
Microsoft considers DAO obsolete[^].
|
|
|
|
|
Mike Dimmick wrote: DAO is not being ported to 64-bit. That is, I believe the 32-bit runtime is still present for a 32-bit application, but there will be no 64-bit runtime. As such, CDaoDatabase will no longer work if you recompile your application for 64-bit.
Ah, well. I knew something had to be going. If the underlying technology is going, then there is no need for the CDao... classes.
|
|
|
|
|
then there is no need for the CDao... classes.
then what is the update replacement for CDao in MFC? any references?
|
|
|
|
|
Sorry, it has been several years since I used MFC.
|
|
|
|
|
hi every one,
when u have an unbound combo box in the datagridview. how do u get the value selected in that combobox. I'm trying to do that and its giving me a nullref exception. I'm working in c# 2.0 windows forms
I was trying to access that with somethin like this
datagridview1["AttendanceComboBoxColumn",i].Value.ToString();
but its not working.
plz help its urgent
thanks in advance!!
Rocky
|
|
|
|
|
i have created a database in sql server7.0 and now i have generated the script from sqlserver 7.0 and i have installed sql serve 8.0
if i connect the database to vb.net i got the answer lik this not associated with trusted trusted sql server connection how do mim clear the error
|
|
|
|
|
The SQL Server does not regocnise the windows account you are using. You need to setup the appropriate windows login on the SQL Server, and then associate it to the appropriate user in the individual databases.
|
|
|
|
|
we have formatted our system and we have installed sql server 2000 version 8.0
previously we have developed using version 7.0 and i have done above still i got the error like that
|
|
|
|
|
Rmesh wrote: we have formatted our system and we have installed sql server 2000 version 8.0
previously we have developed using version 7.0 and i have done above still i got the error like that
Have you tried what I asked? What have you done to "setup the appropriate windows login on the SQL Server, and then associate it to the appropriate user in the individual databases."?
|
|
|
|
|
where i a have to setup the appropriate windows login on sql server
|
|
|
|
|
In SQL Server. I'm sure you'll find it in the SQL Management Studio - In the Security or Logins section (I don't have SQL Server 2005 on this machine so I can't tell you exactly right now)
|
|
|
|
|
i found that if i change that one also but i got the same error .if i change my database from sql version 7.0 to sql version 8.0 if it work or else we have to change the coding in vb.net side
|
|
|
|
|
Sorry - Got confused. (People don't normally talk about version 8.0 and for some reason I thought you were talking about SQL Server 2005)
To set up the logins and users go into the Enterprise Manager and open your server in the tree on the left, open the Security folder and select Logins. From here you can set up the logins.
In the individual database, find the Users area and connect the login to the database user.
|
|
|
|
|
I am working on a project using ASP.NEt 2.0 and Sql server 2005.
My project is working fine but when i make release and install it. It doesnot work infact it doesnot open the connection with the database.
Do good and have good.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
