I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunCommand acCmdDeleteRecord
The subform's recordsource is "select * from tblVisit order by VisitDt"
I'm getting this error message:
Errno is 2465. Err.description is "Can't find field '|' referred to in your
expression"
The record is successfully deleted.
Where should I look for this problem? Completely mystified.
thx in advance for any advice anyone can offer.
Linda
6  8177 
Hi, Linda.
Perhaps you have a similar problem to this one: http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:78*************************@msgid.meganewsser vers.com... I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunCommand acCmdDeleteRecord
The subform's recordsource is "select * from tblVisit order by VisitDt"
I'm getting this error message:
Errno is 2465. Err.description is "Can't find field '|' referred to in
your expression"
The record is successfully deleted.
Where should I look for this problem? Completely mystified.
thx in advance for any advice anyone can offer.
Linda
Gunny,
thx for your advice. My problem is occurring in an Access 2002 (SP3)
database. I have Access 2003 on my laptop. I'll try it there and see if it
performs differently. I guess the good news is that, even though an error
message is generated, the attempt to delete the record is successful...
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote in
message news:khVCd.25840$L7.21511@trnddc05... Hi, Linda.
Perhaps you have a similar problem to this one:
http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:78*************************@msgid.meganewsser vers.com... I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunCommand acCmdDeleteRecord
The subform's recordsource is "select * from tblVisit order by VisitDt"
I'm getting this error message:
Errno is 2465. Err.description is "Can't find field '|' referred to in
your expression"
The record is successfully deleted.
Where should I look for this problem? Completely mystified.
thx in advance for any advice anyone can offer.
Linda
Hi, Linda.
If the problem is due to the bug in MS Office XP SP-3, then the other good
news is that this version is the only version where you'll see this error
message, because Access 2003 and other service packs for MS Office XP don't
have the bug.
If this is the case, then using the menu or either of the RunCommand or
obsolete DoMenuItem methods to delete the record will result in the error
message, but it can be ignored because the record will obviously be deleted.
If you want to avoid the error message, then use VBA code in your command
button's OnClick( ) event such as the following:
' *** Code Start ***
Private Sub DeleteBtn_Click( )
On Error GoTo ErrHandler
Dim db As Database
Dim sqlStmt As String
Dim fOpenedDB As Boolean
sqlStmt = "DELETE * " & _
"FROM tblStuff " & _
"WHERE ID = " & Me!txtID.Value & ";"
Set db = CurrentDb()
fOpenedDB = True
db.Execute sqlStmt, dbFailOnError
Me.Requery
CleanUp:
If (fOpenedDB) Then
db.Close
fOpenedDB = False
End If
Set db = Nothing
Exit Sub
ErrHandler:
MsgBox "Error in DeleteBtn_Click( ) in " & vbCrLf & Me.Name & " form." &
_
vbCrLf & "Error #" & Err.Number & vbCrLf & Err.Description
Err.Clear
GoTo CleanUp
End Sub
' *** Code End ***
In this example, ID is the primary key of the record to be deleted, txtID is
the text box bound to this field, and tblStuff is the name of the table the
form is bound to.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:ef**************************@msgid.meganewsse rvers.com... Gunny,
thx for your advice. My problem is occurring in an Access 2002 (SP3)
database. I have Access 2003 on my laptop. I'll try it there and see if
it performs differently. I guess the good news is that, even though an error
message is generated, the attempt to delete the record is successful...
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote
in message news:khVCd.25840$L7.21511@trnddc05... Hi, Linda.
Perhaps you have a similar problem to this one:
http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:78*************************@msgid.meganewsser vers.com... I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunCommand acCmdDeleteRecord
The subform's recordsource is "select * from tblVisit order by
VisitDt"
I'm getting this error message:
Errno is 2465. Err.description is "Can't find field '|' referred to
in your expression"
The record is successfully deleted.
Where should I look for this problem? Completely mystified.
thx in advance for any advice anyone can offer.
Linda
Hi Gunny,
The database and my original code runs fine on Access 2003. I took the lazy
way out in the Access 2002 version - see below. Really appreciate your
help. I had no idea where to look for any error in my code - since there
was only one statement!! :-)
On Error Resume Next
DoCmd.RunCommand acCmdDeleteRecord
Is this OK or probably bad style and I should have rewritten the code per
your sample code so generously offered below?
thx so much.
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote in
message news:7bdDd.17099$hc7.5636@trnddc06... Hi, Linda.
If the problem is due to the bug in MS Office XP SP-3, then the other good
news is that this version is the only version where you'll see this error
message, because Access 2003 and other service packs for MS Office XP
don't have the bug.
If this is the case, then using the menu or either of the RunCommand or
obsolete DoMenuItem methods to delete the record will result in the error
message, but it can be ignored because the record will obviously be
deleted. If you want to avoid the error message, then use VBA code in your command
button's OnClick( ) event such as the following:
' *** Code Start ***
Private Sub DeleteBtn_Click( )
On Error GoTo ErrHandler
Dim db As Database
Dim sqlStmt As String
Dim fOpenedDB As Boolean
sqlStmt = "DELETE * " & _
"FROM tblStuff " & _
"WHERE ID = " & Me!txtID.Value & ";"
Set db = CurrentDb()
fOpenedDB = True
db.Execute sqlStmt, dbFailOnError
Me.Requery
CleanUp:
If (fOpenedDB) Then
db.Close
fOpenedDB = False
End If
Set db = Nothing
Exit Sub
ErrHandler:
MsgBox "Error in DeleteBtn_Click( ) in " & vbCrLf & Me.Name & " form."
& _
vbCrLf & "Error #" & Err.Number & vbCrLf & Err.Description
Err.Clear
GoTo CleanUp
End Sub
' *** Code End ***
In this example, ID is the primary key of the record to be deleted, txtID
is the text box bound to this field, and tblStuff is the name of the table
the form is bound to.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:ef**************************@msgid.meganewsse rvers.com... Gunny,
thx for your advice. My problem is occurring in an Access 2002 (SP3)
database. I have Access 2003 on my laptop. I'll try it there and see
if it performs differently. I guess the good news is that, even though an
error message is generated, the attempt to delete the record is successful...
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote
in message news:khVCd.25840$L7.21511@trnddc05... Hi, Linda.
Perhaps you have a similar problem to this one:
http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a
message will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:78*************************@msgid.meganewsser vers.com...
> I have a command button on a subform to delete a record.
> The only statement in the subroutine is:
> DoCmd.RunCommand acCmdDeleteRecord
>
> The subform's recordsource is "select * from tblVisit order by
VisitDt" >
> I'm getting this error message:
> Errno is 2465. Err.description is "Can't find field '|' referred to in your
> expression"
>
> The record is successfully deleted.
>
> Where should I look for this problem? Completely mystified.
>
> thx in advance for any advice anyone can offer.
>
> Linda
>
>
>
>
>
Hi, Linda. The database and my original code runs fine on Access 2003. I took the
lazy way out in the Access 2002 version - see below. Really appreciate your
help. I had no idea where to look for any error in my code - since there
was only one statement!! :-)
On Error Resume Next
At least you won't take offense when I tell you that this is the lazy way to
do it. ;-)
The tradeoff to using the code I provided is that there's more code to
maintain. The issue is only a problem in the one version of Access that has
the bug (and this bug may be fixed in the next service pack, if there is
one), so putting in extra effort that no other version of Access needs is a
judgement call.
However, you mentioned that this was the only line of code in the procedure
before you added the "On Error Resume Next" statement, which means that you
didn't have any error handling previously. Personally, I put error handling
in most procedures even if there's only one line of executable code. I do
this because I will know exactly which procedure to look at when something
unexpected happens, and I get the benefit of being shown the error number
and description. Also, the next time I revisit the procedure and need to
add code that ought to have error handling, I don't have to stop to add the
error handling, too.
If the "On Error Resume Next" statement is your preferred method of error
handling, then you _will_ be offended when I tell you that's the lazy way.
I've probably written more than 250,000 lines of VBA code and I've only
found five occasions so far that warranted the "On Error Resume Next"
statement instead of code that either avoided or handled the error.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:89**************************@msgid.meganewsse rvers.com... Hi Gunny,
The database and my original code runs fine on Access 2003. I took the
lazy way out in the Access 2002 version - see below. Really appreciate your
help. I had no idea where to look for any error in my code - since there
was only one statement!! :-)
On Error Resume Next
DoCmd.RunCommand acCmdDeleteRecord
Is this OK or probably bad style and I should have rewritten the code per
your sample code so generously offered below?
thx so much.
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote
in message news:7bdDd.17099$hc7.5636@trnddc06... Hi, Linda.
If the problem is due to the bug in MS Office XP SP-3, then the other
good news is that this version is the only version where you'll see this
error message, because Access 2003 and other service packs for MS Office XP don't have the bug.
If this is the case, then using the menu or either of the RunCommand or
obsolete DoMenuItem methods to delete the record will result in the
error message, but it can be ignored because the record will obviously be
deleted. If you want to avoid the error message, then use VBA code in your
command button's OnClick( ) event such as the following:
' *** Code Start ***
Private Sub DeleteBtn_Click( )
On Error GoTo ErrHandler
Dim db As Database
Dim sqlStmt As String
Dim fOpenedDB As Boolean
sqlStmt = "DELETE * " & _
"FROM tblStuff " & _
"WHERE ID = " & Me!txtID.Value & ";"
Set db = CurrentDb()
fOpenedDB = True
db.Execute sqlStmt, dbFailOnError
Me.Requery
CleanUp:
If (fOpenedDB) Then
db.Close
fOpenedDB = False
End If
Set db = Nothing
Exit Sub
ErrHandler:
MsgBox "Error in DeleteBtn_Click( ) in " & vbCrLf & Me.Name & "
form." & _
vbCrLf & "Error #" & Err.Number & vbCrLf &
Err.Description Err.Clear
GoTo CleanUp
End Sub
' *** Code End ***
In this example, ID is the primary key of the record to be deleted,
txtID is the text box bound to this field, and tblStuff is the name of the table
the form is bound to.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:ef**************************@msgid.meganewsse rvers.com... Gunny,
thx for your advice. My problem is occurring in an Access 2002 (SP3)
database. I have Access 2003 on my laptop. I'll try it there and see
if it performs differently. I guess the good news is that, even though an
error message is generated, the attempt to delete the record is
successful...
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM>
wrote in message news:khVCd.25840$L7.21511@trnddc05...
> Hi, Linda.
>
> Perhaps you have a similar problem to this one:
>
> http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1 >
> HTH.
>
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips.
>
> (Please remove ZERO_SPAM from my reply E-mail address, so that a message > will be forwarded to me.)
>
>
> "Squirrel" <wi*****@covad.net> wrote in message
> news:78*************************@msgid.meganewsser vers.com...
> > I have a command button on a subform to delete a record.
> > The only statement in the subroutine is:
> > DoCmd.RunCommand acCmdDeleteRecord
> >
> > The subform's recordsource is "select * from tblVisit order by
VisitDt" > >
> > I'm getting this error message:
> > Errno is 2465. Err.description is "Can't find field '|' referred
to in > your
> > expression"
> >
> > The record is successfully deleted.
> >
> > Where should I look for this problem? Completely mystified.
> >
> > thx in advance for any advice anyone can offer.
> >
> > Linda
> >
> >
> >
> >
> >
>
>
Hi Gunny,
I wasn't clear. When I said the routine had only one statement I meant one
executable statement
in the body of the routine, excluding error handling.
This is my usual style of error handling, with every routine in a form
module terminating in
this fashion:
Exit_cmdAddRecord_Click:
Exit Sub
Err_cmdAddRecord_Click:
MsgBox Me.Name & vbCrLf & _
Err.Number & vbCrLf & Err.Description & vbCrLf & _
"Patient cmdAddRecord"
Resume Exit_cmdAddRecord_Click
End Sub
and it was due to this error handler that the operation failed while
providing this info:
Errno of 2465. Err.description of "Can't find field '|' referred to in
your expression"
"On Error Resume Next" is not my usual style, I only chose this route
because the 'offending'
statement is good and the operation successful and there are no other
executable statements
in the routine, therefore nothing else can fail. I am shamed nevertheless.
:-)
I REALLY appreciate your sharing your knowledge with me. You're very
generous. Thank you very much.
BTW while testing my database on Access 2003 and discovering no error with
regard the record
deletion operation - good news, something that WAS working in Access 2002,
ungraciously
failed but I did manage to figure this one out by myself! :-)
In Access 2002 this recordsource was accepted for an unbound control on my
form:
=[subformPatientVisit]![cboVisit].[column](0)
Access 2003 required this statement:
=[subformPatientVisit].[Form]![cboVisit].[column](0)
(The Access 2003 version works fine in Access 2002 too.)
thx once again.
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote in
message news:EZVDd.1081$C.762@trnddc05... Hi, Linda.
The database and my original code runs fine on Access 2003. I took the lazy way out in the Access 2002 version - see below. Really appreciate your
help. I had no idea where to look for any error in my code - since
there was only one statement!! :-)
On Error Resume Next
At least you won't take offense when I tell you that this is the lazy way
to do it. ;-)
The tradeoff to using the code I provided is that there's more code to
maintain. The issue is only a problem in the one version of Access that
has the bug (and this bug may be fixed in the next service pack, if there is
one), so putting in extra effort that no other version of Access needs is
a judgement call.
However, you mentioned that this was the only line of code in the
procedure before you added the "On Error Resume Next" statement, which means that
you didn't have any error handling previously. Personally, I put error
handling in most procedures even if there's only one line of executable code. I do
this because I will know exactly which procedure to look at when something
unexpected happens, and I get the benefit of being shown the error number
and description. Also, the next time I revisit the procedure and need to
add code that ought to have error handling, I don't have to stop to add
the error handling, too.
If the "On Error Resume Next" statement is your preferred method of error
handling, then you _will_ be offended when I tell you that's the lazy way.
I've probably written more than 250,000 lines of VBA code and I've only
found five occasions so far that warranted the "On Error Resume Next"
statement instead of code that either avoided or handled the error.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:89**************************@msgid.meganewsse rvers.com... Hi Gunny,
The database and my original code runs fine on Access 2003. I took the lazy way out in the Access 2002 version - see below. Really appreciate your
help. I had no idea where to look for any error in my code - since
there was only one statement!! :-)
On Error Resume Next
DoCmd.RunCommand acCmdDeleteRecord
Is this OK or probably bad style and I should have rewritten the code
per your sample code so generously offered below?
thx so much.
Linda
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote
in message news:7bdDd.17099$hc7.5636@trnddc06... Hi, Linda.
If the problem is due to the bug in MS Office XP SP-3, then the other good news is that this version is the only version where you'll see this error message, because Access 2003 and other service packs for MS Office XP
don't have the bug.
If this is the case, then using the menu or either of the RunCommand
or obsolete DoMenuItem methods to delete the record will result in the error message, but it can be ignored because the record will obviously be
deleted. If you want to avoid the error message, then use VBA code in your command button's OnClick( ) event such as the following:
' *** Code Start ***
Private Sub DeleteBtn_Click( )
On Error GoTo ErrHandler
Dim db As Database
Dim sqlStmt As String
Dim fOpenedDB As Boolean
sqlStmt = "DELETE * " & _
"FROM tblStuff " & _
"WHERE ID = " & Me!txtID.Value & ";"
Set db = CurrentDb()
fOpenedDB = True
db.Execute sqlStmt, dbFailOnError
Me.Requery
CleanUp:
If (fOpenedDB) Then
db.Close
fOpenedDB = False
End If
Set db = Nothing
Exit Sub
ErrHandler:
MsgBox "Error in DeleteBtn_Click( ) in " & vbCrLf & Me.Name & " form." & _
vbCrLf & "Error #" & Err.Number & vbCrLf &
Err.Description Err.Clear
GoTo CleanUp
End Sub
' *** Code End ***
In this example, ID is the primary key of the record to be deleted, txtID is the text box bound to this field, and tblStuff is the name of the
table the form is bound to.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a
message will be forwarded to me.)
"Squirrel" <wi*****@covad.net> wrote in message
news:ef**************************@msgid.meganewsse rvers.com...
> Gunny,
>
> thx for your advice. My problem is occurring in an Access 2002
(SP3) > database. I have Access 2003 on my laptop. I'll try it there and
see if it
> performs differently. I guess the good news is that, even though an
error > message is generated, the attempt to delete the record is
successful... >
> Linda
>
>
> "'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM> wrote in
> message news:khVCd.25840$L7.21511@trnddc05...
> > Hi, Linda.
> >
> > Perhaps you have a similar problem to this one:
> >
> > http://groups.google.co.uk/groups?hl...b0bc52e&rnum=1 > >
> > HTH.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a
message > > will be forwarded to me.)
> >
> >
> > "Squirrel" <wi*****@covad.net> wrote in message
> > news:78*************************@msgid.meganewsser vers.com...
> > > I have a command button on a subform to delete a record.
> > > The only statement in the subroutine is:
> > > DoCmd.RunCommand acCmdDeleteRecord
> > >
> > > The subform's recordsource is "select * from tblVisit order by
VisitDt"
> > >
> > > I'm getting this error message:
> > > Errno is 2465. Err.description is "Can't find field '|'
referred to in
> > your
> > > expression"
> > >
> > > The record is successfully deleted.
> > >
> > > Where should I look for this problem? Completely mystified.
> > >
> > > thx in advance for any advice anyone can offer.
> > >
> > > Linda
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Steve |
last post by:
I have several pairs of synchronized subforms in an application. I have a Delete
button for each pair that uses the following code or similar to delete a record
in the second subform:
...
|
by: Bob |
last post by:
Hi Everybody
I hope you can help.
2 related questions.
1. I am looking for a way to replace the confusing message box that comes up when a user trys to
open a form without putting data in...
|
by: Bob Dydd |
last post by:
Hi everyone
It's me again.
I have an access 2000 database with 12 landscape reports which
sometimes have to be FAXED and other times printed, so I have written
the following code and put it...
|
by: sara |
last post by:
I am getting "Type Mismatch Error" when the following code executes. I
am trying to notify the user if she attempts to add a customer with the
same FirstName, LastName, Address(line1) and City as...
|
by: Susan Bricker |
last post by:
What possible situations (or set of variables) could cause the following
error:
"The command or action 'DeleteRecord' isn't available now." Error
Number = 2046.
The routine that gets the...
|
by: Wayne |
last post by:
I've noticed a behaviour in A2007 that doesn't appear in A2003. The
problem is appearing in a native A2007 database and an A2003 database
running in A2007. If I press a command button to delete a...
|
by: hyperpau |
last post by:
Before anything else, I am not a very technical expert when it comes to VBA coding.
I learned most of what I know by the excellent Access/VBA forum from bytes.com (formerly thescripts.com).
Ergo, I...
|
by: busterbaxter |
last post by:
Hi All,
I got a multiple delete working here but for some reason I occassionally get this error. The way the delete works is there is a text box where the user enters the quantity to delete. If...
|
by: hyperpau |
last post by:
Before anything else, I am not a very technical expert when it comes to VBA coding.
I learned most of what I know by the excellent Access/VBA forum from bytes.com (formerly thescripts.com).
Ergo, I...
|
by: Kemmylinns12 |
last post by:
Blockchain technology has emerged as a transformative force in the business world, offering unprecedented opportunities for innovation and efficiency. While initially associated with cryptocurrencies...
|
by: Naresh1 |
last post by:
What is WebLogic Admin Training?
WebLogic Admin Training is a specialized program designed to equip individuals with the skills and knowledge required to effectively administer and manage Oracle...
|
by: Arjunsri |
last post by:
I have a Redshift database that I need to use as an import data source. I have configured the DSN connection using the server, port, database, and credentials and received a successful connection...
|
by: WisdomUfot |
last post by:
It's an interesting question you've got about how Gmail hides the HTTP referrer when a link in an email is clicked. While I don't have the specific technical details, Gmail likely implements measures...
|
by: Oralloy |
last post by:
Hello Folks,
I am trying to hook up a CPU which I designed using SystemC to I/O pins on an FPGA.
My problem (spelled failure) is with the synthesis of my design into a bitstream, not the C++...
|
by: Rahul1995seven |
last post by:
Introduction:
In the realm of programming languages, Python has emerged as a powerhouse. With its simplicity, versatility, and robustness, Python has gained popularity among beginners and experts...
|
by: Johno34 |
last post by:
I have this click event on my form. It speaks to a Datasheet Subform
Private Sub Command260_Click()
Dim r As DAO.Recordset
Set r = Form_frmABCD.Form.RecordsetClone
r.MoveFirst
Do
If...
|
by: ezappsrUS |
last post by:
Hi,
I wonder if someone knows where I am going wrong below. I have a continuous form and two labels where only one would be visible depending on the checkbox being checked or not. Below is the...
|
by: jack2019x |
last post by:
hello, Is there code or static lib for hook swapchain present?
I wanna hook dxgi swapchain present for dx11 and dx9.
| |
