I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
16  2439 
parez,
Well, tons. Does the mechanism to call the server offer a way to cancel
it? If there is, then this implies that there is an asynchronous method for
calling the server, and you should be taking advantage of that, and not
using the BackgroundWorke r (it's not giving you anything here).
If it doesn't have a way to be called asynchronously, then I would use
the BackgroundWorke r (or some other asynchronous mechanism) and then just
ignore it if you want to cancel the operation.
The thing is, are you doing anything that you need to cancel on the
server as well? If so, you are going to have to roll back the change on the
server, or tell the server to stop somehow.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"parez" <ps*****@gmail. comwrote in message
news:89******** *************** ***********@79g 2000hsk.googleg roups.com...
>
I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
On Jun 3, 2:19 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
parez,
Well, tons. Does the mechanism to call the server offer a way to cancel
it? If there is, then this implies that there is an asynchronous method for
calling the server, and you should be taking advantage of that, and not
using the BackgroundWorke r (it's not giving you anything here).
No there is no way to call it off.(as is) The communication layers is
blocking on a read.
If it doesn't have a way to be called asynchronously, then I would use
the BackgroundWorke r (or some other asynchronous mechanism) and then just
ignore it if you want to cancel the operation.
I thought about it.Since this is a winforms app(and not a web app) , i
thought one extra thread living in the wild shouldnt be a big
problem. But as you correctly guessed I need to cancel the request
also on the server.
The thing is, are you doing anything that you need to cancel on the
server as well? If so, you are going to have to roll back the change on the
server, or tell the server to stop somehow.
There are no rolls backs needed. Just need to make sure that SQL
query, which is taking sometime to execute, stops.
I am connecting to the server over TCP/IP
--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
"parez" <psaw...@gmail. comwrote in message
news:89******** *************** ***********@79g 2000hsk.googleg roups.com...
I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
parez,
You said that there is no way to cancel the operation to the server, but
there is a way to execute the query asynchronously. You can use the
BeginExecute methods on SqlCommand to execute the queries asynchronously,
there is no need for the BackgroundWorke r (IMO).
Basically, if you cancel, then just ignore the callback to the
asynchronous method when it returns (you would have a flag that the callback
would check to see if the operation was cancelled or not).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"parez" <ps*****@gmail. comwrote in message
news:f3******** *************** ***********@w7g 2000hsa.googleg roups.com...
On Jun 3, 2:19 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
>parez,
> Well, tons. Does the mechanism to call the server offer a way to
cancel
it? If there is, then this implies that there is an asynchronous method
for
calling the server, and you should be taking advantage of that, and not
using the BackgroundWorke r (it's not giving you anything here).
No there is no way to call it off.(as is) The communication layers is
blocking on a read.
> If it doesn't have a way to be called asynchronously, then I would
use
the BackgroundWorke r (or some other asynchronous mechanism) and then just
ignore it if you want to cancel the operation.
I thought about it.Since this is a winforms app(and not a web app) , i
thought one extra thread living in the wild shouldnt be a big
problem. But as you correctly guessed I need to cancel the request
also on the server.
> The thing is, are you doing anything that you need to cancel on the
server as well? If so, you are going to have to roll back the change on
the
server, or tell the server to stop somehow.
There are no rolls backs needed. Just need to make sure that SQL
query, which is taking sometime to execute, stops.
I am connecting to the server over TCP/IP
>--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
"parez" <psaw...@gmail. comwrote in message
news:89******* *************** ************@79 g2000hsk.google groups.com...
I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
On Jun 3, 2:38 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
parez,
I am not connecting to sql server. I am sending xml messages over tcp/
ip to a server.
so it would be BeginRead in my situation.
What i am not able to picture is how an async operation in my last
tier(communicat ion tier) going to function?
Maybe thats why i took the easy route of starting the thread in UI.
You said that there is no way to cancel the operation to the server, but
there is a way to execute the query asynchronously. You can use the
BeginExecute methods on SqlCommand to execute the queries asynchronously,
there is no need for the BackgroundWorke r (IMO).
Basically, if you cancel, then just ignore the callback to the
asynchronous method when it returns (you would have a flag that the callback
would check to see if the operation was cancelled or not).
Q2) Also, if i use a flag (which assume would be set by the UI) ,would
it create coupling between the UI and the last tier?
I am not trying to be JA. ;) just trying to stick to my architecture.
After talking to my boss, I found out that even if cancel the thread,
the query will still execute on server.So I might have to go option
2(canceling thread and ignore).
But i still would like to know
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
"parez" <psaw...@gmail. comwrote in message
news:f3******** *************** ***********@w7g 2000hsa.googleg roups.com...
On Jun 3, 2:19 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
parez,
Well, tons. Does the mechanism to call the server offer a way to
cancel
it? If there is, then this implies that there is an asynchronous method
for
calling the server, and you should be taking advantage of that, and not
using the BackgroundWorke r (it's not giving you anything here).
No there is no way to call it off.(as is) The communication layers is
blocking on a read.
If it doesn't have a way to be called asynchronously, then I would
use
the BackgroundWorke r (or some other asynchronous mechanism) and then just
ignore it if you want to cancel the operation.
I thought about it.Since this is a winforms app(and not a web app) , i
thought one extra thread living in the wild shouldnt be a big
problem. But as you correctly guessed I need to cancel the request
also on the server.
The thing is, are you doing anything that you need to cancel on the
server as well? If so, you are going to have to roll back the change on
the
server, or tell the server to stop somehow.
There are no rolls backs needed. Just need to make sure that SQL
query, which is taking sometime to execute, stops.
I am connecting to the server over TCP/IP
--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
"parez" <psaw...@gmail. comwrote in message
>news:89******* *************** ************@79 g2000hsk.google groups.com...
I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
parez,
I misread in regards to issuing the command to SQL Server.
Your boss is correct in that the query will still execute on the server,
so your best bet is to have a flag in the UI layer indicating whether or not
the operation was cancelled. If the flag is true, then when the callback
returns, just ignore it.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"parez" <ps*****@gmail. comwrote in message
news:a8******** *************** ***********@m45 g2000hsb.google groups.com...
On Jun 3, 2:38 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
>parez,
I am not connecting to sql server. I am sending xml messages over tcp/
ip to a server.
so it would be BeginRead in my situation.
What i am not able to picture is how an async operation in my last
tier(communicat ion tier) going to function?
Maybe thats why i took the easy route of starting the thread in UI.
> You said that there is no way to cancel the operation to the server,
but
there is a way to execute the query asynchronously. You can use the
BeginExecute methods on SqlCommand to execute the queries asynchronously,
there is no need for the BackgroundWorke r (IMO).
Basically, if you cancel, then just ignore the callback to the
asynchronous method when it returns (you would have a flag that the
callback
would check to see if the operation was cancelled or not).
Q2) Also, if i use a flag (which assume would be set by the UI) ,would
it create coupling between the UI and the last tier?
I am not trying to be JA. ;) just trying to stick to my architecture.
After talking to my boss, I found out that even if cancel the thread,
the query will still execute on server.So I might have to go option
2(canceling thread and ignore).
But i still would like to know
> - Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
"parez" <psaw...@gmail. comwrote in message
news:f3******* *************** ************@w7 g2000hsa.google groups.com...
On Jun 3, 2:19 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
parez,
> Well, tons. Does the mechanism to call the server offer a way to
cancel
it? If there is, then this implies that there is an asynchronous
method
for
calling the server, and you should be taking advantage of that, and
not
using the BackgroundWorke r (it's not giving you anything here).
No there is no way to call it off.(as is) The communication layers is
blocking on a read.
> If it doesn't have a way to be called asynchronously, then I would
use
the BackgroundWorke r (or some other asynchronous mechanism) and then
just
ignore it if you want to cancel the operation.
I thought about it.Since this is a winforms app(and not a web app) , i
thought one extra thread living in the wild shouldnt be a big
problem. But as you correctly guessed I need to cancel the request
also on the server.
> The thing is, are you doing anything that you need to cancel on
the
server as well? If so, you are going to have to roll back the change
on
the
server, or tell the server to stop somehow.
There are no rolls backs needed. Just need to make sure that SQL
query, which is taking sometime to execute, stops.
I am connecting to the server over TCP/IP
>--
- Nicholas Paldino [.NET/C# MVP]
- m...@spam.guard .caspershouse.c om
>"parez" <psaw...@gmail. comwrote in message
>>news:89****** *************** *************@7 9g2000hsk.googl egroups.com...
I start a BackGroundWorke r to populate a grid. It is started off in
the ui layer
The thread follows( cannot think of a better word) the path
UI->Layer1->Layer2->Communicatio n Layer
and it blocks (the server is executing somthing where which takes
time)
How do i cancel this background worker?
Is there anyway i can access the thread object used by the
backgroundworke r and then stop it?
if i can is there anything wroong with it?
TIA
On Tue, 03 Jun 2008 12:06:27 -0700, parez <ps*****@gmail. comwrote:
On Jun 3, 2:38 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guar d.caspershouse. comwrote:
>parez,
I am not connecting to sql server. I am sending xml messages over tcp/
ip to a server.
so it would be BeginRead in my situation.
Stream.BeginRea d()? You can close the Stream, and the operation will be
completed. Your callback will be called, and EndRead() will (should)
throw an exception.
What i am not able to picture is how an async operation in my last
tier(communicat ion tier) going to function?
See above. How you translate that back up the tiers, depends on your
design.
Maybe thats why i took the easy route of starting the thread in UI.
Does that mean that the UI knows about the communication layer? How does
that keep your tiers separated? :)
[...]
> Basically, if you cancel, then just ignore the callback to the
asynchronous method when it returns (you would have a flag that the
callback
would check to see if the operation was cancelled or not).
Q2) Also, if i use a flag (which assume would be set by the UI) ,would
it create coupling between the UI and the last tier?
I am not trying to be JA. ;) just trying to stick to my architecture.
Not sure what "JA" is. But just because you have a flag, that doesn't
mean that the UI knows about it. It just means that you've got something
in your design that allows the flag to be set by the UI.
What layers need to know about the flag and how they deal with it depend
on your larger design. That's up to you to decide.
After talking to my boss, I found out that even if cancel the thread,
the query will still execute on server.So I might have to go option
2(canceling thread and ignore).
What will the server do if the connection on which the request was made
winds up closed before it can reply?
Ideally, it will just gracefully throw out the query and move on. In that
case, you can safely terminate the operation at the client without
worrying about the impact on the server.
Pete
On Tue, 03 Jun 2008 14:18:58 -0700, parez <ps*****@gmail. comwrote:
1)
My question is how in the communication layer will I know when to
close the stream?How will the UI notify the communication layer?
I don't know. That's dependent on design characterstics that I know
nothing about. It would be up to you to decide what the API between your
layers is/looks like.
The
only advantage I would get by using async reads is ability to close the
socket.
Coz there is nothing else i need to do between BeginRead and EndRead
(other than may be checking the flag)
I don't see how the async/sync API affects this. Even if you used the
sync API, but called it from a thread, you could close the Stream (or
Socket...whatev er it is you're actually using) and an exception would be
thrown, terminating the operation.
What i am not able to picture is how an async operation in my last
tier(communicat ion tier) going to function?
See above. How you translate that back up the tiers, depends on your
design.
2)
If i go down that path , I could throw a custom exception "Cancelled
by User" or send back an xml message (created in the communication
layer) back to the calling tier. The server sends/recieves xml
messages.
Yup. You could. :)
Maybe thats why i took the easy route of starting the thread in UI.
Does that mean that the UI knows about the communication layer? How
does
that keep your tiers separated? :)
3)
What I meant was , start the thread in the UI and then kill the thread
in the UI if needed. This way UI doesn't really care what the Comm
Layer does..
Well, the UI doesn't need to care one way or the other.
But if the communications layer exposes only a synchronous API, then a
higher layer (UI?) will have to wrap that so that the UI itself can
proceed without waiting on the synchronous API. On the other hand, if the
communications layer exposes an async API, it can implement that
internally by wrapping synchronous calls with a thread, or by using
asynchronous calls itself.
Make sure you aren't confusing questions pertaining to the interface
between layers with questions pertaining to how each layer is actually
implemented. :) The two may be related on occasion, but they don't
necessarily restrict answers to the other.
So the solution to my problem could (thats more of a question)
a) Async reads in communication layer and UI shares a flag thru the
tiers with communication layer
The flag is only necessary if your approach to canceling is to let the
operation proceed, but ignore the results. Whether you use a flag to
implement the canceling behavior is independent of whether the
communication layer exposes an async API or not.
or
b) sync reads and Cancel Button should kill(stop) the thread
Nothing should ever "kill" a thread. Any threads you start, they should
complete naturally. You can do this by letting them just finish, or by
providing a way to interrupt the operation (e.g. closing an i/o object).
But please don't go killing threads.
Pete
On Jun 3, 5:37 pm, "Peter Duniho" <NpOeStPe...@nn owslpianmk.com>
wrote:
On Tue, 03 Jun 2008 14:18:58 -0700, parez <psaw...@gmail. comwrote:
1)
My question is how in the communication layer will I know when to
close the stream?How will the UI notify the communication layer?
I don't know. That's dependent on design characterstics that I know
nothing about. It would be up to you to decide what the API between your
layers is/looks like.
The
only advantage I would get by using async reads is ability to close the
socket.
Coz there is nothing else i need to do between BeginRead and EndRead
(other than may be checking the flag)
I don't see how the async/sync API affects this. Even if you used the
sync API, but called it from a thread, you could close the Stream (or
Socket...whatev er it is you're actually using) and an exception would be
thrown, terminating the operation.
1)
If I use sync api, I would be blocking on the read hence not able to
close the socket.
What i am not able to picture is how an async operation in my last
tier(communicat ion tier) going to function?
See above. How you translate that back up the tiers, depends on your
design.
2)
If i go down that path , I could throw a custom exception "Cancelled
by User" or send back an xml message (created in the communication
layer) back to the calling tier. The server sends/recieves xml
messages.
Yup. You could. :)
Maybe thats why i took the easy route of starting the thread in UI.
Does that mean that the UI knows about the communication layer? How
does
that keep your tiers separated? :)
3)
What I meant was , start the thread in the UI and then kill the thread
in the UI if needed. This way UI doesn't really care what the Comm
Layer does..
Well, the UI doesn't need to care one way or the other.
But if the communications layer exposes only a synchronous API, then a
higher layer (UI?) will have to wrap that so that the UI itself can
proceed without waiting on the synchronous API. On the other hand, if the
communications layer exposes an async API, it can implement that
internally by wrapping synchronous calls with a thread, or by using
asynchronous calls itself.
The communication layer exposes a synchronous processmessage method.
Thats why i have the UI create a BackgroundWorke r process so that
the user can navigate around the application when this data is being
retrieved.
Make sure you aren't confusing questions pertaining to the interface
between layers with questions pertaining to how each layer is actually
implemented. :) The two may be related on occasion, but they don't
necessarily restrict answers to the other.
So the solution to my problem could (thats more of a question)
a) Async reads in communication layer and UI shares a flag thru the
tiers with communication layer
The flag is only necessary if your approach to canceling is to let the
operation proceed, but ignore the results. Whether you use a flag to
implement the canceling behavior is independent of whether the
communication layer exposes an async API or not.
The reason why I think it is dependent is because of 1)
or
b) sync reads and Cancel Button should kill(stop) the thread
Nothing should ever "kill" a thread. Any threads you start, they should
complete naturally. You can do this by letting them just finish, or by
providing a way to interrupt the operation (e.g. closing an i/o object).
But please don't go killing threads.
Pete
And I will be nicer to threads.
On Tue, 03 Jun 2008 15:13:55 -0700, parez <ps*****@gmail. comwrote:
The
only advantage I would get by using async reads is ability to close
the
socket.
Coz there is nothing else i need to do between BeginRead and EndRead
(other than may be checking the flag)
I don't see how the async/sync API affects this. Even if you used the
sync API, but called it from a thread, you could close the Stream (or
Socket...whate ver it is you're actually using) and an exception would be
thrown, terminating the operation.
1)
If I use sync api, I would be blocking on the read hence not able to
close the socket.
That's not true. You can't close the socket from the thread that's
blocking, but that's trivially obvious and not relevant. You can close
the socket from whatever thread needs to interrupt the thread that's
blocking. A blocking read can be interrupted just as easily as a
non-blocking read.
Pete This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Bob Alston |
last post by:
Anyone out there successfully deployed Data Access Pages, on a server
they do not control, using RDS in a 3-tier environment? If so I would
like to hear about your success.
From my reading, RDS is not widely available on commercial servers due
to security issues advised by Microsoft (see prior posts). I have done
it successfully in a two tier environment - which (according to
Microsoft) is where the page is on a server, but the access...
|
by: Joey Powell |
last post by:
Re: Original post = Windows forms - how do I get them to render/update
properly? from August 22.
Okay I am making some progress with being able to use delegates to run
my shelled processes on worker threads. Yes I have gotten it to work,
kind-of - that is I have gotten the shelled processes off of the UI
thread (I think?). But the UI still is not updating properly! Still I
have white boxes for forms, label text that does not update, and...
|
by: johkar |
last post by:
I have two problems I cannot work out in the following tab code with
Netscape 6. Problems are marked with all cap comments. One is that
the background image is not shown in NS 6 (two places in CSS). The
second problem is that the top right rounded corner is not showing up
in the Tier 2 tabs. Could you have a look and tell me if it is
possible to correct? This code seems to work fine in IE 5+ and
Firefox. Note that since I can't post...
|
by: Dan Munk |
last post by:
Hello,
I am working on a very large multi-tier Web application. The
application consists of approximately 100 middle-tier/back-end projects
and 200-300 presentation projects. Obviously this is too large to
manage in a single solution. The development staff have each developed
ways to work within such a behemoth structure, but we have not been
able to come up with a standard for project-to-solution organization
and how to manage...
|
by: David Veeneman |
last post by:
Does anyone knmow why an asynchronous worker method would crash if the
e.Cancel method is set to true, but not otherwise?
I'm working on a demo app with an asynchronous call, using the .NET 2.0
BackgroundWorker component. The app works fine if I let the worker method
proceed to completion. But if I cancel the worker method, it crashes.
Specifically, if I set the DoWorkEventArgs.Cancel property to true, the
worker thread crashes at the...
| | |
by: Jon Davis |
last post by:
I have a couple questions. First of all, would anyone consider a
multi-layered programming approach (building business objects that are
seperate from data access logic and seperate from user interface logic but
that interface the UI and the data) an n-tier implementation by definition?
Or does n-tier necessitate a network-distributed architecture (beyond IIS
and SQL Server, i.e. COM+/MTS/MSMQ/WCF) in addition to the layered
programming? If...
|
by: Jesse Aufiero |
last post by:
I'm wondering what the rule is on how to assure that the background worker
'DoWork' routine is truly running entirely in the background. My DoWork
routine calls another procedure which resides in a shared class. This other
procedure has local variables but also refrences class level variables. I'm
wondering if this might cause the DoWork routine to have to reach out to the
primary thread, thus greatly slowing down the routine.
How can...
|
by: Smokey Grindel |
last post by:
I have a search function that runs in a background worker which can run
long.. I want the user to be able to cancel that then run another search...
but sometimes it throws an exception saying
System.InvalidOperationException: This BackgroundWorker is currently busy
and cannot run multiple tasks concurrently.
What I did before the search button was pressed again was check if the
worker is busy and if it is cancel the current search then...
|
by: Infog |
last post by:
I am trying to code a simple background workers class without needing to use the backgroundworker object on a form. This would allow me to use a background worker in any class without writing much additional code. Is it possible to pass in the name of a sub at runtime instead of hard-coding it? To do this I would replace onDoWork and onProgressChanged below and use (Byval onWorkSub as SomeKindOfObject?, Byval onProgressChangedSub as...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
|
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 most users, this new feature is actually very convenient. If you want to control the update process,...
| | |
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 choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
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 launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
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 instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
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 the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| | |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
