I have this:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
Is this considered late binding? If not, what needs changed?
Thanks!
Steve
7  3035 
Yes, that's late binding.
--
Doug Steele, Microsoft Access MVP http://I.Am/DougSteele
(no e-mails, please!)
"PC Datasheet" <no****@nospam. spam> wrote in message
news:1d******** *********@newsr ead2.news.atl.e arthlink.net... I have this:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
Is this considered late binding? If not, what needs changed?
Thanks!
Steve
I stand corrected.
In some earlier threads, I'd said you needed to use CreateObject in this
case.
For some reason, I thought that you needed the Office Objects Library to
access CommandBar items programmaticall y. I just tried that out and
realized I was wrong on that.
I've lost track of who the OP was on this -
the issue seemed to be running this code on machines using different
versions of Access.
There was a reference to a specific version of the Office Objects
Library; it would still be my guess that this reference would not port well
to an earlier version of Access.
If this reference is not needed for other reasons, it should be removed.
If it's needed somewhere else, that place is probably where we need to
look for the problem.
- Turtle
"Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
news:zM******** ************@ro gers.com... Yes, that's late binding.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"PC Datasheet" <no****@nospam. spam> wrote in message
news:1d******** *********@newsr ead2.news.atl.e arthlink.net...I have this:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
Is this considered late binding? If not, what needs changed?
Thanks!
Steve
<< I thought that you needed the Office Objects Library to access
CommandBar items programmaticall y >>
You do if you use:
Dim Cbr As CommandBar
Dim Ctl As Commandbar.Cont rol
I have Office97, 2000 and XP installed and only have Microsoft Office10
Library in my references. Apparently when later versions of Office are
installed, they remove previous versions of the Microsoft Office Library.
I'm creating an Access97 application that needs to manipulate a commandbar
and the controls on the commandbar. That's the reason for all my questions.
The end user of this application will only have MS Office97 installed and
thus Microsoft Office 8 Library in his references. Since I don't have that
reference, I went to late binding with:
Dim Cbr As Object
Dim Ctl As Object
<<it would still be my guess that this reference (Microsoft Office10
Library) would not port well to an earlier version of Access.>>
I think you are very right about this! Upon closer examination, the path to
Microsoft Office10 Library on my computer is:
C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
I presume that the path to references is carried with the database for all
checked references. Therefore, I must assume that the other machine would
never be able to find the Microsoft Office10 Library (mso.dll) because it is
an Office 8 machine and would not even have an Office 10 folder.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:0U******** *********@newsr ead2.news.atl.e arthlink.net... I stand corrected.
In some earlier threads, I'd said you needed to use CreateObject in this
case.
For some reason, I thought that you needed the Office Objects Library to
access CommandBar items programmaticall y. I just tried that out and
realized I was wrong on that.
I've lost track of who the OP was on this -
the issue seemed to be running this code on machines using different
versions of Access.
There was a reference to a specific version of the Office Objects
Library; it would still be my guess that this reference would not port
well to an earlier version of Access.
If this reference is not needed for other reasons, it should be
removed. If it's needed somewhere else, that place is probably where we need to
look for the problem.
- Turtle
"Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
news:zM******** ************@ro gers.com... Yes, that's late binding.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"PC Datasheet" <no****@nospam. spam> wrote in message
news:1d******** *********@newsr ead2.news.atl.e arthlink.net...I have this:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth") Is this considered late binding? If not, what needs changed?
Thanks!
Steve
So what happens if you remove your reference to the Microsoft Office 10
Library?
"Steve" <no****@nospam. spam> wrote in message
news:Xh******** *********@newsr ead2.news.atl.e arthlink.net... << I thought that you needed the Office Objects Library to access
CommandBar items programmaticall y >>
You do if you use:
Dim Cbr As CommandBar
Dim Ctl As Commandbar.Cont rol
I have Office97, 2000 and XP installed and only have Microsoft Office10
Library in my references. Apparently when later versions of Office are
installed, they remove previous versions of the Microsoft Office Library.
I'm creating an Access97 application that needs to manipulate a commandbar
and the controls on the commandbar. That's the reason for all my
questions. The end user of this application will only have MS Office97 installed and
thus Microsoft Office 8 Library in his references. Since I don't have that
reference, I went to late binding with:
Dim Cbr As Object
Dim Ctl As Object
<<it would still be my guess that this reference (Microsoft Office10
Library) would not port well to an earlier version of Access.>>
I think you are very right about this! Upon closer examination, the path
to Microsoft Office10 Library on my computer is:
C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
I presume that the path to references is carried with the database for all
checked references. Therefore, I must assume that the other machine would
never be able to find the Microsoft Office10 Library (mso.dll) because it
is an Office 8 machine and would not even have an Office 10 folder.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:0U******** *********@newsr ead2.news.atl.e arthlink.net... I stand corrected.
In some earlier threads, I'd said you needed to use CreateObject in this
case.
For some reason, I thought that you needed the Office Objects Library to
access CommandBar items programmaticall y. I just tried that out and
realized I was wrong on that.
I've lost track of who the OP was on this -
the issue seemed to be running this code on machines using different
versions of Access.
There was a reference to a specific version of the Office Objects
Library; it would still be my guess that this reference would not port
well to an earlier version of Access.
If this reference is not needed for other reasons, it should be
removed. If it's needed somewhere else, that place is probably where we need
to look for the problem.
- Turtle
"Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
news:zM******** ************@ro gers.com... Yes, that's late binding.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"PC Datasheet" <no****@nospam. spam> wrote in message
news:1d******** *********@newsr ead2.news.atl.e arthlink.net...
>I have this:
> Dim Cbr As Object
> Dim Ctl As Object
> Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> Set Ctl =
>
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth") > Is this considered late binding? If not, what needs changed?
>
> Thanks!
>
> Steve
>
>
I have removed the reference and am using late binding as:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
and all works well.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:vc******** *********@newsr ead2.news.atl.e arthlink.net... So what happens if you remove your reference to the Microsoft Office 10
Library?
"Steve" <no****@nospam. spam> wrote in message
news:Xh******** *********@newsr ead2.news.atl.e arthlink.net... << I thought that you needed the Office Objects Library to access
CommandBar items programmaticall y >>
You do if you use:
Dim Cbr As CommandBar
Dim Ctl As Commandbar.Cont rol
I have Office97, 2000 and XP installed and only have Microsoft Office10
Library in my references. Apparently when later versions of Office are
installed, they remove previous versions of the Microsoft Office
Library. I'm creating an Access97 application that needs to manipulate a
commandbar and the controls on the commandbar. That's the reason for all my questions. The end user of this application will only have MS Office97 installed
and thus Microsoft Office 8 Library in his references. Since I don't have
that reference, I went to late binding with:
Dim Cbr As Object
Dim Ctl As Object
<<it would still be my guess that this reference (Microsoft Office10
Library) would not port well to an earlier version of Access.>>
I think you are very right about this! Upon closer examination, the path
to Microsoft Office10 Library on my computer is:
C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
I presume that the path to references is carried with the database for
all checked references. Therefore, I must assume that the other machine
would never be able to find the Microsoft Office10 Library (mso.dll) because
it is an Office 8 machine and would not even have an Office 10 folder.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:0U******** *********@newsr ead2.news.atl.e arthlink.net... I stand corrected.
In some earlier threads, I'd said you needed to use CreateObject in
this case.
For some reason, I thought that you needed the Office Objects Library
to access CommandBar items programmaticall y. I just tried that out and
realized I was wrong on that.
I've lost track of who the OP was on this -
the issue seemed to be running this code on machines using
different versions of Access.
There was a reference to a specific version of the Office Objects
Library; it would still be my guess that this reference would not port well to an earlier version of Access.
If this reference is not needed for other reasons, it should be
removed. If it's needed somewhere else, that place is probably where we
need to look for the problem.
- Turtle
"Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in
message news:zM******** ************@ro gers.com...
> Yes, that's late binding.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "PC Datasheet" <no****@nospam. spam> wrote in message
> news:1d******** *********@newsr ead2.news.atl.e arthlink.net...
> >I have this:
> > Dim Cbr As Object
> > Dim Ctl As Object
> > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > Set Ctl =
> >
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth") > > Is this considered late binding? If not, what needs changed?
> >
> > Thanks!
> >
> > Steve
> >
> >
>
>
Even on other versions of Access?
"Steve" <no****@nospam. spam> wrote in message
news:Mv******** ******@newsread 3.news.atl.eart hlink.net... I have removed the reference and am using late binding as:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
and all works well.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:vc******** *********@newsr ead2.news.atl.e arthlink.net... So what happens if you remove your reference to the Microsoft Office 10
Library?
"Steve" <no****@nospam. spam> wrote in message
news:Xh******** *********@newsr ead2.news.atl.e arthlink.net... << I thought that you needed the Office Objects Library to access
CommandBar items programmaticall y >>
You do if you use:
Dim Cbr As CommandBar
Dim Ctl As Commandbar.Cont rol
I have Office97, 2000 and XP installed and only have Microsoft
Office10 Library in my references. Apparently when later versions of Office are
installed, they remove previous versions of the Microsoft Office Library. I'm creating an Access97 application that needs to manipulate a commandbar and the controls on the commandbar. That's the reason for all my questions. The end user of this application will only have MS Office97 installed and thus Microsoft Office 8 Library in his references. Since I don't have that reference, I went to late binding with:
Dim Cbr As Object
Dim Ctl As Object
<<it would still be my guess that this reference (Microsoft Office10
Library) would not port well to an earlier version of Access.>>
I think you are very right about this! Upon closer examination, the
path to Microsoft Office10 Library on my computer is:
C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
I presume that the path to references is carried with the database for all checked references. Therefore, I must assume that the other machine would never be able to find the Microsoft Office10 Library (mso.dll) because it is an Office 8 machine and would not even have an Office 10 folder.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:0U******** *********@newsr ead2.news.atl.e arthlink.net...
> I stand corrected.
>
> In some earlier threads, I'd said you needed to use CreateObject in
this > case.
> For some reason, I thought that you needed the Office Objects
Library to > access CommandBar items programmaticall y. I just tried that out and
> realized I was wrong on that.
>
> I've lost track of who the OP was on this -
> the issue seemed to be running this code on machines using different > versions of Access.
> There was a reference to a specific version of the Office
Objects > Library; it would still be my guess that this reference would not
port well
> to an earlier version of Access.
> If this reference is not needed for other reasons, it should be
removed.
> If it's needed somewhere else, that place is probably where we
need to > look for the problem.
>
> - Turtle
>
> "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in
message > news:zM******** ************@ro gers.com...
> > Yes, that's late binding.
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no e-mails, please!)
> >
> >
> >
> > "PC Datasheet" <no****@nospam. spam> wrote in message
> > news:1d******** *********@newsr ead2.news.atl.e arthlink.net...
> > >I have this:
> > > Dim Cbr As Object
> > > Dim Ctl As Object
> > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > Set Ctl =
> > >
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth") > > > Is this considered late binding? If not, what needs changed?
> > >
> > > Thanks!
> > >
> > > Steve
> > >
> > >
> >
> >
>
>
It works in my Access97 database and I have since tried it in Access2000, XP
as 2000 and XP as 2002 and it also worked in all of them.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:2K******** *********@newsr ead2.news.atl.e arthlink.net... Even on other versions of Access?
"Steve" <no****@nospam. spam> wrote in message
news:Mv******** ******@newsread 3.news.atl.eart hlink.net... I have removed the reference and am using late binding as:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
and all works well.
Steve
"MacDermott " <ma********@nos pam.com> wrote in message
news:vc******** *********@newsr ead2.news.atl.e arthlink.net... So what happens if you remove your reference to the Microsoft Office
10 Library?
"Steve" <no****@nospam. spam> wrote in message
news:Xh******** *********@newsr ead2.news.atl.e arthlink.net...
> << I thought that you needed the Office Objects Library to access
> CommandBar items programmaticall y >>
> You do if you use:
> Dim Cbr As CommandBar
> Dim Ctl As Commandbar.Cont rol
> I have Office97, 2000 and XP installed and only have Microsoft Office10 > Library in my references. Apparently when later versions of Office
are > installed, they remove previous versions of the Microsoft Office
Library. > I'm creating an Access97 application that needs to manipulate a
commandbar > and the controls on the commandbar. That's the reason for all my
questions.
> The end user of this application will only have MS Office97
installed and > thus Microsoft Office 8 Library in his references. Since I don't
have that > reference, I went to late binding with:
> Dim Cbr As Object
> Dim Ctl As Object
>
> <<it would still be my guess that this reference (Microsoft Office10
> Library) would not port well to an earlier version of Access.>>
> I think you are very right about this! Upon closer examination, the path to
> Microsoft Office10 Library on my computer is:
> C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
> I presume that the path to references is carried with the database
for all > checked references. Therefore, I must assume that the other machine
would > never be able to find the Microsoft Office10 Library (mso.dll)
because it is
> an Office 8 machine and would not even have an Office 10 folder.
>
> Steve
>
> "MacDermott " <ma********@nos pam.com> wrote in message
> news:0U******** *********@newsr ead2.news.atl.e arthlink.net...
> > I stand corrected.
> >
> > In some earlier threads, I'd said you needed to use CreateObject
in this > > case.
> > For some reason, I thought that you needed the Office Objects
Library to > > access CommandBar items programmaticall y. I just tried that out
and > > realized I was wrong on that.
> >
> > I've lost track of who the OP was on this -
> > the issue seemed to be running this code on machines using
different > > versions of Access.
> > There was a reference to a specific version of the Office
Objects > > Library; it would still be my guess that this reference would not port > well
> > to an earlier version of Access.
> > If this reference is not needed for other reasons, it should
be > removed.
> > If it's needed somewhere else, that place is probably where we
need to
> > look for the problem.
> >
> > - Turtle
> >
> > "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in
message > > news:zM******** ************@ro gers.com...
> > > Yes, that's late binding.
> > >
> > > --
> > > Doug Steele, Microsoft Access MVP
> > > http://I.Am/DougSteele
> > > (no e-mails, please!)
> > >
> > >
> > >
> > > "PC Datasheet" <no****@nospam. spam> wrote in message
> > > news:1d******** *********@newsr ead2.news.atl.e arthlink.net...
> > > >I have this:
> > > > Dim Cbr As Object
> > > > Dim Ctl As Object
> > > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > > Set Ctl =
> > > >
> Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth") > > > > Is this considered late binding? If not, what needs changed?
> > > >
> > > > Thanks!
> > > >
> > > > Steve
> > > >
> > > >
> > >
> > >
> >
> >
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Mike MacSween |
last post by:
Had some trouble with Word automation. Sorted it, in the process thought I
would try late binding. Some people reccomend it. So this:
*********************************************************
Public Sub MailMerge(strQuery As String, strTemplate As String)
snip
Dim doc As Word.Document
Dim wrdApp As Word.Application
snip
Set wrdApp = New Word.Application
|
by: JD Kronicz |
last post by:
Hi .. I have an issue I have been beating my head against
the wall on for some time. I am trying to use late
binding for MS graph so that my end users don't have to
worry about having the right version of the MS Graph type
library. Up until now I have been walking them through
the process of setting the references to include their
version of MS Graph library.
My problem is that I can not seem to get the syntax
correct .. or perhaps...
|
by: Composer |
last post by:
I've read many postings about the problem of Access.References.IsBroken
and the consensus seems to be that late binding is the cure-all.
I have a very complex Access application that needs hundreds of lines
of code to format a Word document in a very specific way.
Because my clients have various versions of Word, the problem of broken
references comes up. I wish Microsoft had implemented a reasonable
solution, so that VBA could do...
|
by: Zlatko Matiæ |
last post by:
I was reading about late binding, but I'm not completely sure what is to be
done in order to adjust code to late binding...
For example, I'm not sure if this is correct:
early binding:
Dim ws As DAO.Workspace
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim rs As DAO.Recordset
|
by: eBob.com |
last post by:
In another thread VJ made me aware of Tag. Fantastic! I've been
wanting this capability for a long time. But it seems that I cannot
use it with Option Strict On. In an event handler I have ...
Private Sub chkbxSelI_Click(ByVal sender As Object, ByVal e As
System.EventArgs)
MsgBox("bingo for number " & sender.Tag.ToString)
End Sub
| | |
by: lgbjr |
last post by:
hi All,
I've decided to use Options Strict ON in one of my apps and now I'm trying
to fix a late binding issue. I have 5 integer arrays:
dim IA1(500), IA2(500), IA3(500), IA4(500), IA5(500) as integer
The integers in these arrays are actually pointers to different columns of
data in a text file.
|
by: Tim Roberts |
last post by:
I've been doing COM a long time, but I've just come across a behavior
with late binding that surprises me. VB and VBS are not my normal
milieux, so I'm hoping someone can point me to a document that
describes this.
Here's the setup. We have a COM server, written in Python. For
completeness, here is the script:
----- testserver.py -----
import pythoncom
|
by: GS |
last post by:
I have installed the ms PIA for ofc XP, and followed the article
http://support.microsoft.com/kb/247412/
trying to paste into a worksheet
However I got late binding not allowed errors
....
webOCWraooer,Copy // get the desired data into clapboard
|
by: ADezii |
last post by:
The process of verifying that an Object exists and that a specified Property or Method is valid is called Binding. There are two times when this verification process can take place: during compile time (Early Binding) or run time (Late Binding). When you declare an Object Variable as a specific Data Type, you are using Early Binding so the verification can take place during compile time. When you declare a Variable of the generic Object Data...
|
by: Siv |
last post by:
hi,
I am converting an application that writes to an Excel spreadsheet and the
code trips the "option Strict" that I would like on because the parser says
"option Strict On disallows late binding", I am struggling to understand why
I am tripping this error.
This is the code that causes the problems:
XLApp.Goto("MonthTitleTL") 'Goes to bookmark in sheet
r = XLApp.ActiveCell.Row 'sets variable r equal
|
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: 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 captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
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: 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 into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
| | |
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?
| |
