473,574 Members | 2,269 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Returning Focus to Main Form

OK, this is a stupid thing, but I can't seem to get this to work. I have a
form with a subform (in continuous form view). A combo box on the main form
has code in the AfterUpdate event which adds a record to the subform (based
on the value of the combo box) and requeries the subform control. I want the
focus to return to the combo box on the main form when it's done, but I
can't get it to do so if the user enters a value and presses Enter (which
tabs to the next control, which is the subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil
Nov 13 '05 #1
17 3844
I think you're setting yourself up for some failure here. How will your code
let the user leave the textbox at all if you intercept a focus move and
don't let the focus go elsewhere? If you put code on the textbox to stop the
focus move, that is what will happen.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user move
the focus if he/she presses Tab key or clicks into another control), but I
would think that your users will get very tired of having to remember that
the Enter key won't work to move along for just that one control on the
form.

I suggest that you think of a different approach for what you want to
achieve.

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I have a
form with a subform (in continuous form view). A combo box on the main
form has code in the AfterUpdate event which adds a record to the subform
(based on the value of the combo box) and requeries the subform control. I
want the focus to return to the combo box on the main form when it's done,
but I can't get it to do so if the user enters a value and presses Enter
(which tabs to the next control, which is the subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil

Nov 13 '05 #2
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?
If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that I
want to move the focus back to the combo box. Thus, if the user enters a
value and hits Enter, the result is that the focus is back in the combo box.
If the user is just tabbing through the controls, pressing Enter or Tab,
they can leave it fine. No code is activated.
If you put code on the textbox to stop the focus move, that is what will
happen.
Again, just in AfterUpdate.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.
Not what I want.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user move
the focus if he/she presses Tab key or clicks into another control), but I
would think that your users will get very tired of having to remember that
the Enter key won't work to move along for just that one control on the
form.
Again, don't want that. Just AfterUpdate.

I suggest that you think of a different approach for what you want to
achieve.
Hopefully my above notes have clarified what I'm trying to do here.

Neil

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I have
a form with a subform (in continuous form view). A combo box on the main
form has code in the AfterUpdate event which adds a record to the subform
(based on the value of the combo box) and requeries the subform control.
I want the focus to return to the combo box on the main form when it's
done, but I can't get it to do so if the user enters a value and presses
Enter (which tabs to the next control, which is the subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil


Nov 13 '05 #3
OK. Put a hidden textbox on the form -- name it txtNoGo. Set its
DefaultValue to 0.

In your textbox's AfterUpdate event, use this code:

Private Sub TextBoxName_Aft erUpdate()
Me.txtNoGo = 1
End Sub
In the textbox's Exit event, use this code:

Private Sub TextBoxName_Exi t(Cancel As Integer)
If Me.txtNoGo = 1 Then
Me.txtNoGo = 0
Cancel = True
End If

This will use a hidden textbox as a flag to know that you've updated the
textbox's value and that the focus should not move.

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:kd******** *********@newsr ead3.news.pas.e arthlink.net...
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?


If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that I
want to move the focus back to the combo box. Thus, if the user enters a
value and hits Enter, the result is that the focus is back in the combo
box. If the user is just tabbing through the controls, pressing Enter or
Tab, they can leave it fine. No code is activated.
If you put code on the textbox to stop the focus move, that is what will
happen.


Again, just in AfterUpdate.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.


Not what I want.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user move
the focus if he/she presses Tab key or clicks into another control), but
I would think that your users will get very tired of having to remember
that the Enter key won't work to move along for just that one control on
the form.


Again, don't want that. Just AfterUpdate.

I suggest that you think of a different approach for what you want to
achieve.


Hopefully my above notes have clarified what I'm trying to do here.

Neil

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I have
a form with a subform (in continuous form view). A combo box on the main
form has code in the AfterUpdate event which adds a record to the
subform (based on the value of the combo box) and requeries the subform
control. I want the focus to return to the combo box on the main form
when it's done, but I can't get it to do so if the user enters a value
and presses Enter (which tabs to the next control, which is the
subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil



Nov 13 '05 #4
FYI... I note that I mistakenly referred to your control as a textbox in my
replies. Code will work for combo box as well.
--

Ken Snell
<MS ACCESS MVP>

"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:kd******** *********@newsr ead3.news.pas.e arthlink.net...
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?


If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that I
want to move the focus back to the combo box. Thus, if the user enters a
value and hits Enter, the result is that the focus is back in the combo
box. If the user is just tabbing through the controls, pressing Enter or
Tab, they can leave it fine. No code is activated.
If you put code on the textbox to stop the focus move, that is what will
happen.


Again, just in AfterUpdate.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.


Not what I want.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user move
the focus if he/she presses Tab key or clicks into another control), but
I would think that your users will get very tired of having to remember
that the Enter key won't work to move along for just that one control on
the form.


Again, don't want that. Just AfterUpdate.

I suggest that you think of a different approach for what you want to
achieve.


Hopefully my above notes have clarified what I'm trying to do here.

Neil

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I have
a form with a subform (in continuous form view). A combo box on the main
form has code in the AfterUpdate event which adds a record to the
subform (based on the value of the combo box) and requeries the subform
control. I want the focus to return to the combo box on the main form
when it's done, but I can't get it to do so if the user enters a value
and presses Enter (which tabs to the next control, which is the
subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil



Nov 13 '05 #5
Understood.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..
FYI... I note that I mistakenly referred to your control as a textbox in
my replies. Code will work for combo box as well.
--

Ken Snell
<MS ACCESS MVP>

"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:kd******** *********@newsr ead3.news.pas.e arthlink.net...
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?


If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that
I want to move the focus back to the combo box. Thus, if the user enters
a value and hits Enter, the result is that the focus is back in the combo
box. If the user is just tabbing through the controls, pressing Enter or
Tab, they can leave it fine. No code is activated.
If you put code on the textbox to stop the focus move, that is what
will happen.


Again, just in AfterUpdate.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.


Not what I want.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user
move the focus if he/she presses Tab key or clicks into another
control), but I would think that your users will get very tired of
having to remember that the Enter key won't work to move along for just
that one control on the form.


Again, don't want that. Just AfterUpdate.

I suggest that you think of a different approach for what you want to
achieve.


Hopefully my above notes have clarified what I'm trying to do here.

Neil

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I
have a form with a subform (in continuous form view). A combo box on
the main form has code in the AfterUpdate event which adds a record to
the subform (based on the value of the combo box) and requeries the
subform control. I want the focus to return to the combo box on the
main form when it's done, but I can't get it to do so if the user
enters a value and presses Enter (which tabs to the next control, which
is the subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil



Nov 13 '05 #6
Interesting approach. You'd think it would be possible to do it directly in
code. I seem to recall in the past that I was able to do that, by just using
SetFocus. I don't know if I'm remembering wrongly, or if something's
changed.

In any case, your solution works fine in the case where the user presses
Enter after entering a value. But it has problems in other scenarios:

* If the user uses the mouse to select a value from the combo box and then
presses Enter to leave the combo box , the focus stays in the combo box.

* Similarly, if the user uses the mouse to select a value and then clicks a
command button or tries to go to a new record, they are still stuck there
for at least one time.

Perhaps something in the KeyPress event, instead of Exit, would work? (Still
seems there should be a more direct approach....)

Thanks,

Neil

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:eY******** ******@TK2MSFTN GP12.phx.gbl...
OK. Put a hidden textbox on the form -- name it txtNoGo. Set its
DefaultValue to 0.

In your textbox's AfterUpdate event, use this code:

Private Sub TextBoxName_Aft erUpdate()
Me.txtNoGo = 1
End Sub
In the textbox's Exit event, use this code:

Private Sub TextBoxName_Exi t(Cancel As Integer)
If Me.txtNoGo = 1 Then
Me.txtNoGo = 0
Cancel = True
End If

This will use a hidden textbox as a flag to know that you've updated the
textbox's value and that the focus should not move.

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:kd******** *********@newsr ead3.news.pas.e arthlink.net...
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?


If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that
I want to move the focus back to the combo box. Thus, if the user enters
a value and hits Enter, the result is that the focus is back in the combo
box. If the user is just tabbing through the controls, pressing Enter or
Tab, they can leave it fine. No code is activated.
If you put code on the textbox to stop the focus move, that is what
will happen.


Again, just in AfterUpdate.

You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.


Not what I want.

Even if you trap to determine if the Enter key was pressed, and stop the
focus move only if that key is pressed (in other words, let the user
move the focus if he/she presses Tab key or clicks into another
control), but I would think that your users will get very tired of
having to remember that the Enter key won't work to move along for just
that one control on the form.


Again, don't want that. Just AfterUpdate.

I suggest that you think of a different approach for what you want to
achieve.


Hopefully my above notes have clarified what I'm trying to do here.

Neil

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
OK, this is a stupid thing, but I can't seem to get this to work. I
have a form with a subform (in continuous form view). A combo box on
the main form has code in the AfterUpdate event which adds a record to
the subform (based on the value of the combo box) and requeries the
subform control. I want the focus to return to the combo box on the
main form when it's done, but I can't get it to do so if the user
enters a value and presses Enter (which tabs to the next control, which
is the subform). I've tried:

Me.SetFocus
Me.MyCombo.SetF ocus

which doesn't seem to work. Any ideas?

Thanks,

Neil



Nov 13 '05 #7
Neil Ginsberg wrote:
Interesting approach. You'd think it would be possible to do it directly in
code.


The Windows API SetFocus is sometimes a bit more responsive than the
Access SetFocus.

We may be able to use it as follows (mostly air ... code)

Private Declare Function SetFocusAPI _
Lib "user32" _
Alias "SetFocus" _
(ByVal hwnd As Long) _
As Long

Private Sub Label10_Click()
SetFocusAPI Form_MDACandESO .hwnd
End Sub

where MDACandESO is the name of the form to which focus is transferred.
We must use the Alias, of course, to avoid confusion with the Access
function.

In a not so thorough test of two forms this moves the focus to the form
called MDACandESO. This form must have a module for the nomenclature
Form_MDACandESO to work. I'm guessing one could use Forms("MDACandE SO")
if it doesn't have a module, but I haven't tried that.

Of course, one might want to write some error handling code if one could
not be sure that Form_MDACandESO is open, or test its state with SysCmd.

Lyle
Nov 13 '05 #8
You can only cancel the movement of the focus by cancelling the Exit or
BeforeUpdate event. You can use the GotFocus event of a subsequent control
to move the focus to another control -- perhaps that is what you're thinking
of.

The scenarios that you mention are along the lines of what I'd posted
initially. Until you can identify what is a change that should not let the
focus move and what is not a change that should not let the focus move, it's
difficult to devise a 'perfect fit' for your scenario. As I'd mentioned
previously, you could try trapping for the Enter key being pressed and use
that to decide if the flag should be set or not, along with the AfterUpdate
changes.

You'll need to figure out the exact scenarios that should move focus and/or
the ones that shouldn't, and then develop the setup to handle the form's
actions the way you wish.
--

Ken Snell
<MS ACCESS MVP>

"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:15******** *********@newsr ead1.news.pas.e arthlink.net...
Interesting approach. You'd think it would be possible to do it directly
in code. I seem to recall in the past that I was able to do that, by just
using SetFocus. I don't know if I'm remembering wrongly, or if something's
changed.

In any case, your solution works fine in the case where the user presses
Enter after entering a value. But it has problems in other scenarios:

* If the user uses the mouse to select a value from the combo box and then
presses Enter to leave the combo box , the focus stays in the combo box.

* Similarly, if the user uses the mouse to select a value and then clicks
a command button or tries to go to a new record, they are still stuck
there for at least one time.

Perhaps something in the KeyPress event, instead of Exit, would work?
(Still seems there should be a more direct approach....)

Thanks,

Neil

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:eY******** ******@TK2MSFTN GP12.phx.gbl...
OK. Put a hidden textbox on the form -- name it txtNoGo. Set its
DefaultValue to 0.

In your textbox's AfterUpdate event, use this code:

Private Sub TextBoxName_Aft erUpdate()
Me.txtNoGo = 1
End Sub
In the textbox's Exit event, use this code:

Private Sub TextBoxName_Exi t(Cancel As Integer)
If Me.txtNoGo = 1 Then
Me.txtNoGo = 0
Cancel = True
End If

This will use a hidden textbox as a flag to know that you've updated the
textbox's value and that the focus should not move.

--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:kd******** *********@newsr ead3.news.pas.e arthlink.net...
See below.

"Ken Snell [MVP]" <kt***********@ ncoomcastt.rena etl> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
I think you're setting yourself up for some failure here. How will your
code let the user leave the textbox at all if you intercept a focus move
and don't let the focus go elsewhere?

If you mean that the user will never be able to leave the combo box with
what I'm doing, that's not true. It's only in the AfterUpdate event that
I want to move the focus back to the combo box. Thus, if the user enters
a value and hits Enter, the result is that the focus is back in the
combo box. If the user is just tabbing through the controls, pressing
Enter or Tab, they can leave it fine. No code is activated.

If you put code on the textbox to stop the focus move, that is what
will happen.

Again, just in AfterUpdate.
You could use the Exit event to intercept the focus move, but that will
happen whenever the user tries to leave the textbox.

Not what I want.
Even if you trap to determine if the Enter key was pressed, and stop
the focus move only if that key is pressed (in other words, let the
user move the focus if he/she presses Tab key or clicks into another
control), but I would think that your users will get very tired of
having to remember that the Enter key won't work to move along for just
that one control on the form.

Again, don't want that. Just AfterUpdate.
I suggest that you think of a different approach for what you want to
achieve.

Hopefully my above notes have clarified what I'm trying to do here.

Neil
--

Ken Snell
<MS ACCESS MVP>
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:4i******** *********@newsr ead1.news.pas.e arthlink.net...
> OK, this is a stupid thing, but I can't seem to get this to work. I
> have a form with a subform (in continuous form view). A combo box on
> the main form has code in the AfterUpdate event which adds a record to
> the subform (based on the value of the combo box) and requeries the
> subform control. I want the focus to return to the combo box on the
> main form when it's done, but I can't get it to do so if the user
> enters a value and presses Enter (which tabs to the next control,
> which is the subform). I've tried:
>
> Me.SetFocus
> Me.MyCombo.SetF ocus
>
> which doesn't seem to work. Any ideas?
>
> Thanks,
>
> Neil
>



Nov 13 '05 #9
Thanks for the tip. I added the code you gave to the subform, and created a
Label10 label, but there was no effect. Perhaps because the subform is part
of the main form, by setting focus to the main form we're not changing
anything?

In any case, since you said you got it to work, I'm wondering what your
setup was. Was one form a subform of the other?

Thanks,

Neil
"Lyle Fairfield" <ly******@yahoo .ca> wrote in message
news:uR******** **********@read 1.cgocable.net. ..
Neil Ginsberg wrote:
Interesting approach. You'd think it would be possible to do it directly
in code.


The Windows API SetFocus is sometimes a bit more responsive than the
Access SetFocus.

We may be able to use it as follows (mostly air ... code)

Private Declare Function SetFocusAPI _
Lib "user32" _
Alias "SetFocus" _
(ByVal hwnd As Long) _
As Long

Private Sub Label10_Click()
SetFocusAPI Form_MDACandESO .hwnd
End Sub

where MDACandESO is the name of the form to which focus is transferred. We
must use the Alias, of course, to avoid confusion with the Access
function.

In a not so thorough test of two forms this moves the focus to the form
called MDACandESO. This form must have a module for the nomenclature
Form_MDACandESO to work. I'm guessing one could use Forms("MDACandE SO") if
it doesn't have a module, but I haven't tried that.

Of course, one might want to write some error handling code if one could
not be sure that Form_MDACandESO is open, or test its state with SysCmd.

Lyle

Nov 13 '05 #10

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

Similar topics

14
4523
by: Mark | last post by:
Hi, At the top of my php file I have got :- <body onblur="self.focus();"> so when I click off onto another window, my window comes back up in front which is perfect. The problem however, is that when I try to type into my form boxes, the key transfers are all being lost (i.e. keyboard is disabled)!
5
10114
by: Petec | last post by:
Is there a way to prevent a form from getting focus? Thanks! - Pete
1
5038
by: cider123 | last post by:
I've tried working with the SelectedIndices and Items.Selected attributes to get the problem to go away, but not having any luck. Questions I have are: 1) How do you move (using code) the focus Rectangle when your Selected Index changes ? 2) If there are no selected rows, can that focus rectangle be removed? 3) What other quirks exist in...
2
5395
by: Sid Price | last post by:
Is there a way of stopping a form getting focus in VB.NET. The scenario I have is a main form and a form used for display only. There are no user controls on the display form and it does not ever need to have the focus. When the displays on the form are updated it appears to get the focus. I would like to prevent this because if the user...
3
4239
by: jan.loucka | last post by:
Hi, I looked around for this specific problem but could not find any answer - there's few things in VB but still nothing exactly like this so I'd appreciate any help. We're writing C# WinForm application that need to "silently" use another app (called MapInfo) within itself - the intention is to use this app (which is quite sophisticated...
0
4088
by: cyberdawg999 | last post by:
Greetings all in ASP land I have overcome one obstacle that took me 2 weeks to overcome and I did it!!!!! I am so elated!! thank you to all who invested their time and energy towards helping me with my problems. Now for my new little problem,I had a problem posting the values from checkbox fields to a database and thats the obstacle I...
3
3147
by: Johnny Jörgensen | last post by:
I've a form that opens a tool window. The problem is that when the tool window is opened, the main form itself passes focus to the toolwindow. What I want and need is a toolwindow that works like a control with tabstop=false, i.e. it doesn't get focus when the window is opened, but focus is retained at the main form. And when you click a...
21
3818
vikas251074
by: vikas251074 | last post by:
I am getting error while entry in userid field. When user enter his user id, an event is fired immediately and user id is verified using AJAX method. But I am getting error 'Object doesn't support this property or method'. <form name="myform" action="main.asp" method="post"> <div id="content"> <h2 id="pageName">Main Page</h2> <div...
5
3335
by: oscWork | last post by:
Does anyone know of any way to switch focus between a main form and a child form without the usual flickering you get while changing focus between windows? This works fine if the main form is an MDI container and the child form is within that container, but MDI is not appropriate for this application. I would like to be able to interact with a...
0
7826
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
0
8085
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
8126
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
0
6491
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
5637
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
5328
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
3763
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
3781
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
1362
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.