Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when I
try to execute
11  3423 
"ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when I
try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem pertains
to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
"ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when I
try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem pertains
to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
ColdCanuck wrote: "ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when I
try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem
pertains to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
CC,
In the stored procedure definition you want to specify a SPECIFIC NAME as
well as the procedure name.
You really do want to be using the enumeration adCmdStoredProc, which you
have commented out in favour of adCmdText.
You'll find a couple of good samples in -
C:\PROGRAM FILES\SQLLIB\SAMPLES\ADO\VB
From memory they are something like spcall.* (simple call) and rssp.*
(returning a result set).
I was just working on an example piece of code for one of our developers
today and the sample code works !!!
HTH
Phil
ColdCanuck wrote: "ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when I
try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem
pertains to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
CC,
In the stored procedure definition you want to specify a SPECIFIC NAME as
well as the procedure name.
You really do want to be using the enumeration adCmdStoredProc, which you
have commented out in favour of adCmdText.
You'll find a couple of good samples in -
C:\PROGRAM FILES\SQLLIB\SAMPLES\ADO\VB
From memory they are something like spcall.* (simple call) and rssp.*
(returning a result set).
I was just working on an example piece of code for one of our developers
today and the sample code works !!!
HTH
Phil
"Philip Nelson" <te*****@scotdb.com> wrote in message
news:Mq***********************@news.easynews.com.. . In the stored procedure definition you want to specify a SPECIFIC NAME as
well as the procedure name.
You really do want to be using the enumeration adCmdStoredProc, which you
have commented out in favour of adCmdText.
You'll find a couple of good samples in -
C:\PROGRAM FILES\SQLLIB\SAMPLES\ADO\VB
From memory they are something like spcall.* (simple call) and rssp.*
(returning a result set).
I was just working on an example piece of code for one of our developers
today and the sample code works !!!
HTH
Phil
Thanks for that info Phil!
I have stepped back from the VB part and am focussing on the DB2 part. I
have added SPECIFIC NAME to the procedure npn_test2, but when I try to run
it via Ops Navigator: call npn_test2('000006', ?);
I get the following error: "The number of parameter values set or registered
does not match the number of parameters."
Yet when I run:
SELECT SCHEMA, SPECIFIC_NAME, ORDINAL_POSITION, PARAMETER_MODE,
PARAMETER_NAME
FROM qsys2.sysparms
WHERE specific_name ='NORM';
I get:
NORM, NPN_TEST2, 1, IN, PCONTACTID
NORM, NPN_TEST2, 2, OUT, ONAME
So what's up with this error message?
cheers,
Norm
"Philip Nelson" <te*****@scotdb.com> wrote in message
news:Mq***********************@news.easynews.com.. . In the stored procedure definition you want to specify a SPECIFIC NAME as
well as the procedure name.
You really do want to be using the enumeration adCmdStoredProc, which you
have commented out in favour of adCmdText.
You'll find a couple of good samples in -
C:\PROGRAM FILES\SQLLIB\SAMPLES\ADO\VB
From memory they are something like spcall.* (simple call) and rssp.*
(returning a result set).
I was just working on an example piece of code for one of our developers
today and the sample code works !!!
HTH
Phil
Thanks for that info Phil!
I have stepped back from the VB part and am focussing on the DB2 part. I
have added SPECIFIC NAME to the procedure npn_test2, but when I try to run
it via Ops Navigator: call npn_test2('000006', ?);
I get the following error: "The number of parameter values set or registered
does not match the number of parameters."
Yet when I run:
SELECT SCHEMA, SPECIFIC_NAME, ORDINAL_POSITION, PARAMETER_MODE,
PARAMETER_NAME
FROM qsys2.sysparms
WHERE specific_name ='NORM';
I get:
NORM, NPN_TEST2, 1, IN, PCONTACTID
NORM, NPN_TEST2, 2, OUT, ONAME
So what's up with this error message?
cheers,
Norm
"ColdCanuck" <co**@canuck.ca> wrote in message
news:577mc.7147$F04.4921@clgrps13... "ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when
I try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem
pertains to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
Hey CC,
Just judging by the error message you're getting (never having to use DB2
before) I would guess that your problem is that you are calling the
cmd.Parameters.Refresh method, which should auto-populate your Parameter
collection in the Command object, and then incorrectly creating 2 other
parameters to add to the collection.
The two new Parameters that you are creating as new.
This is an incorrect way to create parameters. You should call the
Cmd.CreateParameter method to create the parameter, set the values, and then
append it to the Paramters collection.
The bottom line is that you should only do one of the two-
Cmd.Parameters.Refresh (Which is inefficient if the parameter list doesn't
change), or Cmd.Parameters.Append(Cmd.CreateParameter(...)) (my personal
favorite).
--Buddy Robbins
MCSD, MCSE, MCDBA
"ColdCanuck" <co**@canuck.ca> wrote in message
news:577mc.7147$F04.4921@clgrps13... "ColdCanuck" <co**@canuck.ca> wrote in message
news:gY6mc.6987$F04.5734@clgrps13... Greetings!
I am VERY new to DB2 but not Orable, Sybase and SQL Server.
I am trying to call a stored procedure via VB 6 and ADO/OLEDB. But when
I try to execute
Sorry, I accidently sent this before finishing...
Please excuse the cross-post but I am unsure which group my problem
pertains to.
As I was saying, when I try to execute my stored proc, I get the following
error:
"Parameter type cannot be determined for at least one variant
parameter."
My proc is quite simple:
CREATE PROCEDURE NORM.npn_test2
( IN pContactId character(3),
OUT oName character(20))
LANGUAGE SQL
BEGIN ATOMIC
DECLARE sName CHAR(20);
SET sName = (SELECT ADADTX || ', ' || ADAETX FROM MAILIB.UUADCPP WHERE
ADAANB = pContactId);
SET oName = sName;
END
My VB code looks like:
Public Function Call_sp_test(con As ADODB.Connection, ByVal sContactId As
String) As String
On Error GoTo ErrHandler
Dim sName As String
Dim cmd As New ADODB.Command
Dim rst As New ADODB.Recordset
Dim P1 As New ADODB.Parameter
Dim P2 As New ADODB.Parameter
Set cmd.ActiveConnection = con
cmd.CommandText = "{CALL NORM.npn_test2(?,?)}"
cmd.CommandType = adCmdText
'cmd.CommandType = adCmdStoredProc
cmd.Parameters.Refresh
'cmd.Parameters("pContactId").Value = sContactId
cmd.Prepared = True
sName = " " '40 spaces
P1.Direction = adParamInput
P1.Type = adChar
P1.Size = 6
P1.Name = "ContactId"
P1.Value = "000006"
P1.Direction = adParamReturnValue
P2.Type = adChar
P2.Name = "Name"
P2.Size = 40
P2.Value = sName
cmd.Parameters.Append P1
cmd.Parameters.Append P2
'cmd.Execute
rst.Open cmd <- error occurs here
sName = cmd.Parameters("oName").Value
Call_sp_test = cmd.Parameters("oName").Value
rst.Close
Set rst = Nothing
Set cmd = Nothing
ErrHandler:
MsgBox "Error Code: " & Err.Number & vbNewLine & _
"Description: " & Err.Description & vbNewLine & _
"Source: " & Err.Source, vbOKOnly + vbCritical
Err.Clear
'Set Call_sp_test = Nothing
End Function
Has anyone run into this problem before? What am I missing here?
Thanks for all replies!
cheers,
CC
Hey CC,
Just judging by the error message you're getting (never having to use DB2
before) I would guess that your problem is that you are calling the
cmd.Parameters.Refresh method, which should auto-populate your Parameter
collection in the Command object, and then incorrectly creating 2 other
parameters to add to the collection.
The two new Parameters that you are creating as new.
This is an incorrect way to create parameters. You should call the
Cmd.CreateParameter method to create the parameter, set the values, and then
append it to the Paramters collection.
The bottom line is that you should only do one of the two-
Cmd.Parameters.Refresh (Which is inefficient if the parameter list doesn't
change), or Cmd.Parameters.Append(Cmd.CreateParameter(...)) (my personal
favorite).
--Buddy Robbins
MCSD, MCSE, MCDBA
"Buddy Robbins" <Bu***********@sbcglobal.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hey CC,
Just judging by the error message you're getting (never having to use DB2
before) I would guess that your problem is that you are calling the
cmd.Parameters.Refresh method, which should auto-populate your Parameter
collection in the Command object, and then incorrectly creating 2 other
parameters to add to the collection.
The two new Parameters that you are creating as new.
This is an incorrect way to create parameters. You should call the
Cmd.CreateParameter method to create the parameter, set the values, and
then append it to the Paramters collection.
The bottom line is that you should only do one of the two-
Cmd.Parameters.Refresh (Which is inefficient if the parameter list doesn't
change), or Cmd.Parameters.Append(Cmd.CreateParameter(...)) (my personal
favorite).
--Buddy Robbins
MCSD, MCSE, MCDBA
Thanks for that Buddy!
I've taken this back to the DB2 where I'm getting errors just trying to call
the stored proc.
cheers,
Norm
"Buddy Robbins" <Bu***********@sbcglobal.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hey CC,
Just judging by the error message you're getting (never having to use DB2
before) I would guess that your problem is that you are calling the
cmd.Parameters.Refresh method, which should auto-populate your Parameter
collection in the Command object, and then incorrectly creating 2 other
parameters to add to the collection.
The two new Parameters that you are creating as new.
This is an incorrect way to create parameters. You should call the
Cmd.CreateParameter method to create the parameter, set the values, and
then append it to the Paramters collection.
The bottom line is that you should only do one of the two-
Cmd.Parameters.Refresh (Which is inefficient if the parameter list doesn't
change), or Cmd.Parameters.Append(Cmd.CreateParameter(...)) (my personal
favorite).
--Buddy Robbins
MCSD, MCSE, MCDBA
Thanks for that Buddy!
I've taken this back to the DB2 where I'm getting errors just trying to call
the stored proc.
cheers,
Norm The bottom line is that you should only do one of the two-
Cmd.Parameters.Refresh (Which is inefficient if the parameter list
doesn't change), or Cmd.Parameters.Append(Cmd.CreateParameter(...)) (my
personal favorite).
--Buddy Robbins
MCSD, MCSE, MCDBA
You were spot on here Buddy! That did it!
many thanks...
Norm This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Jen S |
last post by:
I feel like I'm missing something obvious here, but I'm stumped...
I have a stored procedure with code that looks like:
INSERT INTO MyTableA ( ...fields... ) VALUES (...values...)
IF...
|
by: xAvailx |
last post by:
I have a requirement that requires detection of rows deleted/updated by
other processes. My business objects call stored procedures to create,
read, update, delete data in a SQL Server 2000 data...
|
by: Nyul |
last post by:
Gurus,
I have a verb big problem which I'm unable to explain.
We have a DB2 V6.1.0 on AIX 4.3
I want to make a C stored procedure which at the end will be called by a PHP
script.
The...
|
by: Dave Sisk |
last post by:
I've created a system or external trigger on an AS/400 file a.k.a DB2 table.
(Note this is an external trigger defined with the ADDPFTRG CL command, not
a SQL trigger defined with the CREATE...
|
by: Rhino |
last post by:
I am getting an sqlcode of -927 when I execute SQL within a COBOL stored
procedure in DB2 OS/390 Version 6 on OS/390. I have looked at the error
message for that condition and tried everything I...
|
by: Eric Land |
last post by:
Help! I'm trying to call a parameterized stored proc in ASP.NET in VB. I am
creating a command object and creating a parametr list, and assigning a value
from a session variable (this is working)...
|
by: hicks |
last post by:
I'm trying to invoke a DB2 stored procedure. The stored proc is coded
in C and compiled to a shared library, which has been placed in the
<DB2 dir>/functions directory. The platform is Solaris....
|
by: ravindrag |
last post by:
Hi,
I am getting error SQL1131N during sqlj.install_jar(...). There is no useful message in the diag.log (even with diag level 4). I am giving the diag.log entries at the end of this posting...
|
by: db2user24 |
last post by:
I'm trying to invoke a DB2 stored procedure. The stored proc is coded
in C and compiled to a shared library, which has been placed in the
<DB2 dir>/functions directory. The platform is Linux (using...
|
by: mirandacascade |
last post by:
Questions toward the bottom of the post.
Situation is this:
1) Access 97
2) SQL Server 2000
3) The Access app:
a) sets up pass-thru query
b) .SQL property of querydef is a string, the...
|
by: lllomh |
last post by:
Define the method first
this.state = {
buttonBackgroundColor: 'green',
isBlinking: false, // A new status is added to identify whether the button is blinking or not
}
autoStart=()=>{
|
by: DJRhino |
last post by:
Was curious if anyone else was having this same issue or not....
I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM)
The start time is equivalent to 19:00 (7PM) in Central...
|
by: giovanniandrean |
last post by:
The energy model is structured as follows and uses excel sheets to give input data:
1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
|
by: NeoPa |
last post by:
Hello everyone.
I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report).
I know it can be done by selecting :...
|
by: NeoPa |
last post by:
Introduction
For this article I'll be using a very simple database which has Form (clsForm) & Report (clsReport) classes that simply handle making the calling Form invisible until the Form, or all...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM)
Please note that the UK and Europe revert to winter time on...
|
by: isladogs |
last post by:
The next online meeting of the Access Europe User Group will be on Wednesday 6 Dec 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, Mike...
|
by: GKJR |
last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...
| |
