473,545 Members | 1,989 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Error on: DoCmd.RunComman d acCmdDeleteReco rd

I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunComman d acCmdDeleteReco rd

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

Nov 13 '05 #1
6 8441
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.megane wsservers.com.. .
I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunComman d acCmdDeleteReco rd

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


Nov 13 '05 #2
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.orgZE RO_SPAM> wrote in
message news:khVCd.2584 0$L7.21511@trnd dc05...
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.megane wsservers.com.. .
I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunComman d acCmdDeleteReco rd

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



Nov 13 '05 #3
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.megan ewsservers.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.orgZE RO_SPAM> wrote in message news:khVCd.2584 0$L7.21511@trnd dc05...
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.megane wsservers.com.. .
I have a command button on a subform to delete a record.
The only statement in the subroutine is:
DoCmd.RunComman d acCmdDeleteReco rd

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




Nov 13 '05 #4
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.RunComman d acCmdDeleteReco rd

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.orgZE RO_SPAM> wrote in
message news:7bdDd.1709 9$hc7.5636@trnd dc06...
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.megan ewsservers.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.orgZE RO_SPAM> wrote

in
message news:khVCd.2584 0$L7.21511@trnd dc05...
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.megane wsservers.com.. .
> I have a command button on a subform to delete a record.
> The only statement in the subroutine is:
> DoCmd.RunComman d acCmdDeleteReco rd
>
> 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
>
>
>
>
>



Nov 13 '05 #5
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.megan ewsservers.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.RunComman d acCmdDeleteReco rd

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.orgZE RO_SPAM> wrote in message news:7bdDd.1709 9$hc7.5636@trnd dc06...
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.megan ewsservers.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.orgZE RO_SPAM> wrote in
message news:khVCd.2584 0$L7.21511@trnd dc05...
> 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.megane wsservers.com.. .
> > I have a command button on a subform to delete a record.
> > The only statement in the subroutine is:
> > DoCmd.RunComman d acCmdDeleteReco rd
> >
> > 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
> >
> >
> >
> >
> >
>
>



Nov 13 '05 #6
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_cmdAddReco rd_Click:
Exit Sub

Err_cmdAddRecor d_Click:
MsgBox Me.Name & vbCrLf & _
Err.Number & vbCrLf & Err.Description & vbCrLf & _
"Patient cmdAddRecord"
Resume Exit_cmdAddReco rd_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:
=[subformPatientV isit]![cboVisit].[column](0)
Access 2003 required this statement:
=[subformPatientV isit].[Form]![cboVisit].[column](0)

(The Access 2003 version works fine in Access 2002 too.)

thx once again.
Linda
"'69 Camaro" <Fo************ **************@ Spameater.orgZE RO_SPAM> 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.megan ewsservers.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.RunComman d acCmdDeleteReco rd

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.orgZE RO_SPAM> wrote

in
message news:7bdDd.1709 9$hc7.5636@trnd dc06...
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.megan ewsservers.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.orgZE RO_SPAM> wrote in
> message news:khVCd.2584 0$L7.21511@trnd dc05...
> > 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.megane wsservers.com.. .
> > > I have a command button on a subform to delete a record.
> > > The only statement in the subroutine is:
> > > DoCmd.RunComman d acCmdDeleteReco rd
> > >
> > > 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
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

8
4039
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: DoCmd.SetWarnings False DoCmd.RunCommand acCmdDeleteRecord DoCmd.SetWarnings True End If ExitHere: Me!SubName.SetFocus
5
744
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 it. ie ..Syntax Error(Missing Operator) In queryexpression '=" & Me! DoCmd.OpenForm stDocName, , , stLinkCriteria
1
5574
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 in a module to bring up the print dialog: Public Function PrintAccess()
19
2068
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 one that already exists on the file. If there is a match, ask the user and cancel the record add if she sees that it's a dup customer. I had...
0
4003
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 error is (comments left in to show various solutions that all get the same results (error message above):
2
4379
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 record on a single form using DoCmd.RunCommand acCmdDeleteRecord as the code behind the button, when I close that form Access asks me if I want to...
2
19416
hyperpau
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 will be writing this article intended for those who are in the same level, or maybe lower, of my technical knowledge. I would be using layman's...
16
3357
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 it is blank it will delete 1 item. It never fails when I delete just 1 item but if I delete more than one item it fails but only some times. Here is...
0
2897
hyperpau
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 will be writing this article intended for those who are in the same level, or maybe lower, of my technical knowledge. I would be using layman's...
0
7680
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
7934
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
1
7446
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
0
6003
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then...
1
5349
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
4966
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
0
3476
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in...
0
3459
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
1033
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.