|
Can only tell you how i do it with ODBC. There are Escape-Sequences, i.e. '{d 26-03-02}', the driver will convert it to a date your DB can understand.
dirk
|
|
|
|
|
Hi Dirk,
thanks in advance for your support
Fortunatly I resolved my problem!!
Simply instead of pass the datetime value to my SP,I pass the TCHAR string and inside the SP use the CONVERT function.
In this manner in the C++ side (server) I can pass simply a BSTR parameter.
Bye
Andrea
|
|
|
|
|
Hi all
I m trying to learn VC++ database prog. in this regard i need help if
someone can create a small sample app as follows:
> IDE = VC++ 6
> Using ADO DSN less connection (Provider='' user='' password='' data source='')
> db contains two tables (table_a, table_b)
>each table contain 3 fields of datatypes Numeric, Char, Date
>data must populate in Edit Boxes via SQL statement which stored behind a button
>other buttons Add Update Delete (Add/Update will not work automatically as in Access or VB)
>data validation of table_a thru table_b during Add/Editing
I will be very grateful. This will help alot to understand VC database programing.
|
|
|
|
|
|
Hello,
Is their a Critical section function on store procedure? Or what is the counter part of CriticalSection of C in store procedure script?
|
|
|
|
|
What are you trying to do?
You can lock tables, etc... yourself if you want, but that could slow your whole architecture down.
Cheers,
Simon
"I ask candidates to create an object model of a chicken.", Bruce Eckel on interviewing programmers.
animation mechanics in SVG (latest pic 1) (latest pic 2)
|
|
|
|
|
Yeah, you should by default allow SQL to handle locking. If you concern is that all processes should complete or fail look at
BEGIN TRANSACTION
ROLLBACK TRANSACTION
COMMIT TRANSACTION
|
|
|
|
|
Hi,
I need to migrate an old database under Visual Fox Pro 3.0 to SQL Server 2000. I was looking around to got the connectionString for the olddbConnection object but I can't find anything.
I've tried to use the this one :
("Provider=MSDASQL; Persist Security Info=False;Data Source=Test")
but I got the following error message :
The .Net Data OLE DB Provider(System.Data.OleDb) does not support the MSDASQL Provider, Microsoft OLE DB Provider for ODBC Drivers.
Does anyone know how to read data from Fox Pro ?
Thanx
Sybux
|
|
|
|
|
|
|
|
Sure it is possible.
<br />
Create Table #tempTable<br />
(ID INT IDENTITY,<br />
col1 type,<br />
col2 type,<br />
...)<br />
<br />
Insert Into #tempTable (col1, col2, ...)<br />
Select col1, col2, ...<br />
From .....<br />
<br />
<br />
Select * from #tempTable<br />
This will add an incremented ID to the temp table, you can then select from.
Hope this helps.
Jeremy Oldham
|
|
|
|
|
|
This solution is for Oracle, I don't know if and how you can use it in other systems:
SELECT rownum, col1, col2, col3 FROM table;
--
karl
|
|
|
|
|
Hi,
I have created a DLL which access the DAO objects (specially MSAccess
databases). In the code I create the CDaoRecordset with the new operator,
like this:
CDaoRecordset * CDaoClass::Query(CString query)
{
CDaoRecordset * pNewRecord = new CDaoRecordset(&m_pDatabase);
pNewRecord->Open(AFX_DAO_USE_DEFAULT_TYPE, query, 0);
return pNewRecord;
}
CDaoClass::CloseRecordSet(CDaoRecordset * pRecord)
{
pRecord->Close();
delete pRecord;
}
This works just as it should if the classes are in the main application,
but I'm getting an exception when in DLL the CDaoRecordset::Open() method
is executed. The other DAO methods are working fine, so I can list the
tables, change them, create indexes, relationships, etc. But I can't
execute queries that returns data.
When debugging the application I found out that there is an exception in
DAOCORE.CPP line 4855, shown bellow:
void CDaoRecordset::BuildSelectList()
{
ASSERT_VALID(this);
ASSERT(m_nFields > 0); // This line will assert since m_nFields is 0
m_strSQL += _afxSelect2;
CDaoFieldExchange fx(CDaoFieldExchange::AddToSelectList, this);
DoFieldExchange(&fx);
}
Does anyone have any clues about it?
Thanks in advance.
Crercio O. Silva / DBTools
Crercio O. Silva / DBTools Development
http://www.dbtools.com.br
|
|
|
|
|
http://www.theregister.co.uk/content/53/29419.html
Oh what a tnagled web we weave, when what we use is not free!
Use PostgreSQL (www.postgresql.org) instead!
PS. Native Windows port coming soon. In the meantime, you can run it under Cygwin.
|
|
|
|
|
|
Makes you wonder what other MS Licenses may have holes in them. But did anyone figure out exactly what pieces they are barking about? Sounds like Olap/Analysis services but maybe even DTS as well.
|
|
|
|
|
I need to create a table programatically in MS Access with
a field having data type AutoNumber.
I am using VC++ tool and ADO and Catalog Smartpointer for creation of tables.
Send me suggessions how to do it.
With Thanks & Regards
Kamesh
|
|
|
|
|
I have a problem with SQLDMO, in my MFC Application I use DMO to restore/backup a SQL DB; when I specify a path that contains blank spaces DMO fail to perform the operation because the resulting path is a merge from my path and the default one.
i.e. mypath = "D:\My Folder" resulting path =" C:\ProgramFiles\Microsoft SQL Server\.......\My Folder"
Can anyone suggest me any possible solutions ?
Thank you all!!!!
|
|
|
|
|
Please post you code example. Also if you are using the .RelocateFiles proterty of the SQLRestore method are you putting [] around the path data as required. Keep in mind this is a multipart string and requires the []'s.
Is this by chance joecre from the CodeGuru boards?
|
|
|
|
|
Yes i am......thank you again
|
|
|
|
|
I have this very weird problem - when I invoke a stored procedure from ASP, it complained that one of the input parameter was "declared" as OUTPUT but the ASP call indicated otherwise. Error message as follows:
"Microsoft OLE DB Provider for SQL Server error '80040e14'
Formal parameter '@employee_division_code' was defined as OUTPUT but the actual parameter not declared OUTPUT."
I have checked, and double checked. The parameter was defined as INPUT parameter in SQL server stored procedure. I have included both signature of stored procedure, and the ASP/ADO API call below - hope one of you wiz can help me spot a problem that I failed to spot. Please look for <PROBLEM> tag - that's how I highlight the problem.
(1) Here's the stored procedure:
CREATE PROC dbo.sproc_AddUser
@login char(15) =NULL,
@password char(15) =NULL,
@first_name char(50) =NULL,
@middle_name char(50) =NULL,
@last_name char(50) =NULL,
@email1 char(50) =NULL,
@email2 char(50) =NULL,
@tel_home char(30) =NULL,
@tel_office char(30) =NULL,
@tel_fax char(30) =NULL,
@tel_cell char(30) =NULL,
@tel_pager char(30) =NULL,
@title char(100) =NULL,
@association char(50) =NULL,
@address_unit_num char(15) =NULL,
@address_bldg_name char(50) =NULL,
@address_street_num char(15) =NULL,
@address_street char(100) =NULL,
@address_city char(100) =NULL,
@address_province char(100) =NULL,
@address_country char(100) =NULL,
@address_zipcode char(100) =NULL,
@employee_division_code char(500)='EMPLOYEE, REGUSER',
@customer_division_code char(500)='CUST, REGUSER',
@seniority_level int=0,
@cust_service_level int=0,
@bAdminStatus int=0, ********** <PROBLEM> **********
@bEmployStatus int=0,
@bClientStatus int=0,
@error_status int OUTPUT
WITH RECOMPILE
AS
...
...
...
(2) Here's fragment of my ASP script:
Set oCmd = Server.CreateObject("ADODB.Command")
With oCmd
.ActiveConnection = oConn
.CommandText = "sproc_AddUser"
.CommandType = adCmdStoredProc
.Parameters.Append .CreateParameter("@login", adChar, adParamInput, 15, Request.Form("txtLogin") )
.Parameters.Append .CreateParameter("@password", adChar, adParamInput, 15, Request.Form("txtPasswd") )
.Parameters.Append .CreateParameter("@first_name", adChar, adParamInput, 50, Request.Form("first_name") )
.Parameters.Append .CreateParameter("@middle_name", adChar, adParamInput, 50, Request.Form("middle_name") )
.Parameters.Append .CreateParameter("@last_name", adChar, adParamInput, 50, Request.Form("last_name") )
.Parameters.Append .CreateParameter("@email1", adChar, adParamInput, 50, Request.Form("email1") )
.Parameters.Append .CreateParameter("@email2", adChar, adParamInput, 50, Request.Form("email2") )
.Parameters.Append .CreateParameter("@tel_home", adChar, adParamInput, 30, Request.Form("tel_home") )
.Parameters.Append .CreateParameter("@tel_office", adChar, adParamInput, 30, Request.Form("tel_office") )
.Parameters.Append .CreateParameter("@tel_fax", adChar, adParamInput, 30, Request.Form("tel_fax") )
.Parameters.Append .CreateParameter("@tel_cell", adChar, adParamInput, 30, Request.Form("tel_cell") )
.Parameters.Append .CreateParameter("@tel_pager", adChar, adParamInput, 30, Request.Form("tel_pager") )
.Parameters.Append .CreateParameter("@title", adChar, adParamInput, 100, Request.Form("title") )
.Parameters.Append .CreateParameter("@association", adChar, adParamInput, 50, Request.Form("association") )
.Parameters.Append .CreateParameter("@address_unit_num", adChar, adParamInput, 15, Request.Form("address_unit_num") )
.Parameters.Append .CreateParameter("@address_bldg_name", adChar, adParamInput, 50, Request.Form("address_bldg_name") )
.Parameters.Append .CreateParameter("@address_street_num", adChar, adParamInput, 15, Request.Form("address_street_num") )
.Parameters.Append .CreateParameter("@address_street", adChar, adParamInput, 100, Request.Form("address_street") )
.Parameters.Append .CreateParameter("@address_city", adChar, adParamInput, 100, Request.Form("address_city") )
.Parameters.Append .CreateParameter("@address_province", adChar, adParamInput, 100, Request.Form("address_province") )
.Parameters.Append .CreateParameter("@address_country", adChar, adParamInput, 100, Request.Form("address_country") )
.Parameters.Append .CreateParameter("@address_zipcode", adChar, adParamInput, 100, Request.Form("address_zipcode") )
.Parameters.Append .CreateParameter("@bAdminStatus", adInteger, adParamInput, 4, bAdminStatus) ********** <PROBLEM> **********
.Parameters.Append .CreateParameter("@bEmployStatus", adInteger, adParamInput, 4, bEmployStatus)
.Parameters.Append .CreateParameter("@bClientStatus", adInteger, adParamInput, 4, bClientStatus)
.Parameters.Append .CreateParameter("@cust_service_level", adInteger, adParamInput, 5, CInt(Request.Form("cust_service_level")) )
.Parameters.Append .CreateParameter("@error_status", adInteger, adParamOutput, 4, 0) 'OUTPUT: error status.
'Execute the stored procedure:
.Execute()
End With
Thanks a bunch.
norm
|
|
|
|
|
i have experienced this before.
despite the fact that parameters are named, you still need to create the right number and the right type of paramers in the ADODB.Command object. basically, what is happening is that the parameters you are passing from vb are not lining up with the proc paramaters the way you think they are.
declare your vb parameter list identically to the sp param list, including the ones you don't realy need (don't set a value for them in vb if you want to use the SPs default values).
it will work then.
#include <beer.h>
|
|
|
|
|
thanks. yes, the orders of parameters in asp script is NOT the same as that as defined in stored procedure - I took time to make sure the parameter NAME ana TYPE matches however. Didnt expect the order would matter too.
Just hope that this is the root of the problem. Will work on it later today and will let you know what happen.
norm
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)