Dear Access Developers,
The 'Allow Additions' property of my form is causing unexpected
results.
I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all. By simply adjusting the 'Allow
Additions' property back to 'Yes', the form behaves correctly once
more and shows all the expected records (as well as the unsightly
'new' record).
I understand that the detail section of a form will be completely
blank if a) there are no records to display and b) no new records can
be added. But there definitely are records to display so I am confused
as to why the records are not being displayed.
Surely my form should still show the expected records?
Do any Access Gurus know what the problem is? Could you be kind enough
to suggest a solution?
My only idea is to rebuild all of the functionality of my form in a
report. This wouldn't be ideal as some of the behavior of my form
wouldn't map well or easily to a report, so any other suggestions
would be welcomed.
Thank you for your help and expertise,
Cro
6  3176 
Something else is wrong here.
Are you certain you have not set the Data Entry property of the form to Yes
as well? That will prevent existing records being loaded.
Alternatively, is anything filtering the form?
Or, is there anything in the SQL statement that is depending on a value in
the form? Or perhaps a calculated field that could have its data type
misunderstood?
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com... Dear Access Developers,
The 'Allow Additions' property of my form is causing unexpected
results.
I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all. By simply adjusting the 'Allow
Additions' property back to 'Yes', the form behaves correctly once
more and shows all the expected records (as well as the unsightly
'new' record).
I understand that the detail section of a form will be completely
blank if a) there are no records to display and b) no new records can
be added. But there definitely are records to display so I am confused
as to why the records are not being displayed.
Surely my form should still show the expected records?
Do any Access Gurus know what the problem is? Could you be kind enough
to suggest a solution?
My only idea is to rebuild all of the functionality of my form in a
report. This wouldn't be ideal as some of the behavior of my form
wouldn't map well or easily to a report, so any other suggestions
would be welcomed.
Thank you for your help and expertise,
Cro
Hi Allen,
Thanks for replying. It is nice to know that a developer who "knows
more about Access than any other developer in Australia" is helping
out a developer in England who can't fathom out the side effects of
the 'Allow Additions' form property. Are you certain you have not set the Data Entry property of the form to Yes
as well? That will prevent existing records being loaded.
Data Entry is and always has been set to 'No'.
Alternatively, is anything filtering the form?
Nothing is or ever has been filtering the form.
Or, is there anything in the SQL statement that is depending on a value in
the form? Or perhaps a calculated field that could have its data type
misunderstood?
This is my SQL statement:
SELECT tblStaffHours.*
FROM tblStaffHours
WHERE (((Forms!frmSta ffHours!txtDate )=tblStaffHours .Date));
You can see that the SQL statement does rely on a value in the form,
namely a date value. The user can increment and decrement this date
value (as well as jump to today and tomorrow's date) with command
buttons. The 'On Click' event of these command buttons first adjusts
the value within the date text box ('txtDate') and performs a requery
on the form ("DoCmd.Requery "), so that the SQL statement (that is the
record source of the form) is re-invoked.
How would the fact that the SQL statement relies on something in the
form affect its behavior? This is especially confusing as the form
behaves correctly when 'Allow Additions' is set to 'Yes', but the form
behaves very differently (as described in the first post of this
thread) when 'Allow Additions' is set to 'No'.
Incidentally, I have a second form using this exact same concept
(adjusting 'txtDate' to load appropriate records) that works
perfectly. For this second form, I need to be able to add records and
so 'Allow Additions' is set to 'Yes'. This form also fails in the same
way when 'Allow Additions' is set to 'No'.
Thank you for your help with this problem. It is very much
appreciated.
Regards,
Cro
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message news:<40******* *************** @per-qv1-newsreader-01.iinet.net.au >... Something else is wrong here.
Are you certain you have not set the Data Entry property of the form to Yes
as well? That will prevent existing records being loaded.
Alternatively, is anything filtering the form?
Or, is there anything in the SQL statement that is depending on a value in
the form? Or perhaps a calculated field that could have its data type
misunderstood?
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com... Dear Access Developers,
The 'Allow Additions' property of my form is causing unexpected
results.
I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all. By simply adjusting the 'Allow
Additions' property back to 'Yes', the form behaves correctly once
more and shows all the expected records (as well as the unsightly
'new' record).
I understand that the detail section of a form will be completely
blank if a) there are no records to display and b) no new records can
be added. But there definitely are records to display so I am confused
as to why the records are not being displayed.
Surely my form should still show the expected records?
Do any Access Gurus know what the problem is? Could you be kind enough
to suggest a solution?
My only idea is to rebuild all of the functionality of my form in a
report. This wouldn't be ideal as some of the behavior of my form
wouldn't map well or easily to a report, so any other suggestions
would be welcomed.
Thank you for your help and expertise,
Cro
Cro wrote: I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all.
Post the SQL statement.
Okay there is a cyclic dependency here. The form's RecordSource depends on a
value in the form, and the form doesn't get its value until the RecordSource
is loaded.
Particularly, when AllowAdditions is No, it is possible that the form will
have no record at all (as distinct form having the New Record when
AllowAdditions is Yes). When you have no records at all in a form - not even
the new record - the entire detail section goes blank, and trying to refer
to one of the non-existent text boxes causes an error. In addition, there
are bugs in the way Access handles and displays the values in sections other
than the detail section, as discussed in: http://allenbrowne.com/bug-06.html
So, it seems that the RecordSource's depenency on a value from the form is
preventing it from loading any records at all when AllowAdditions is No.
There are several workarounds. One would be to programmaticall y assign a
value to the RecordSource of the form after txtDate changes. Another would
be to leave AllowAdditions to Yes, and cancel Form_BeforeInse rt event to
prevent any new records.
BTW, if you really do have a field named "Date", there is a good chance that
Access will get that confused as well. In VBA, Date is a reserved word (for
the system date).
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com...
Thanks for replying. It is nice to know that a developer who "knows
more about Access than any other developer in Australia" is helping
out a developer in England who can't fathom out the side effects of
the 'Allow Additions' form property.
Are you certain you have not set the Data Entry property of the form to
Yes as well? That will prevent existing records being loaded.
Data Entry is and always has been set to 'No'.
Alternatively, is anything filtering the form?
Nothing is or ever has been filtering the form.
Or, is there anything in the SQL statement that is depending on a value
in the form? Or perhaps a calculated field that could have its data type
misunderstood?
This is my SQL statement:
SELECT tblStaffHours.*
FROM tblStaffHours
WHERE (((Forms!frmSta ffHours!txtDate )=tblStaffHours .Date));
You can see that the SQL statement does rely on a value in the form,
namely a date value. The user can increment and decrement this date
value (as well as jump to today and tomorrow's date) with command
buttons. The 'On Click' event of these command buttons first adjusts
the value within the date text box ('txtDate') and performs a requery
on the form ("DoCmd.Requery "), so that the SQL statement (that is the
record source of the form) is re-invoked.
How would the fact that the SQL statement relies on something in the
form affect its behavior? This is especially confusing as the form
behaves correctly when 'Allow Additions' is set to 'Yes', but the form
behaves very differently (as described in the first post of this
thread) when 'Allow Additions' is set to 'No'.
Incidentally, I have a second form using this exact same concept
(adjusting 'txtDate' to load appropriate records) that works
perfectly. For this second form, I need to be able to add records and
so 'Allow Additions' is set to 'Yes'. This form also fails in the same
way when 'Allow Additions' is set to 'No'.
Thank you for your help with this problem. It is very much
appreciated.
Regards,
Cro
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:<40******* *************** @per-qv1-newsreader-01.iinet.net.au >... Something else is wrong here.
Are you certain you have not set the Data Entry property of the form to
Yes as well? That will prevent existing records being loaded.
Alternatively, is anything filtering the form?
Or, is there anything in the SQL statement that is depending on a value
in the form? Or perhaps a calculated field that could have its data type
misunderstood?
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com... Dear Access Developers,
The 'Allow Additions' property of my form is causing unexpected
results.
I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all. By simply adjusting the 'Allow
Additions' property back to 'Yes', the form behaves correctly once
more and shows all the expected records (as well as the unsightly
'new' record).
I understand that the detail section of a form will be completely
blank if a) there are no records to display and b) no new records can
be added. But there definitely are records to display so I am confused
as to why the records are not being displayed.
Surely my form should still show the expected records?
Do any Access Gurus know what the problem is? Could you be kind enough
to suggest a solution?
My only idea is to rebuild all of the functionality of my form in a
report. This wouldn't be ideal as some of the behavior of my form
wouldn't map well or easily to a report, so any other suggestions
would be welcomed.
Thank you for your help and expertise,
Cro
GD <gy**********@j mjservices.com> wrote in message news:<EW******* ********@fe1.co lumbus.rr.com>. .. Cro wrote: I am developing a form that has its 'Default View' property set to
'Continuous Forms' and am displaying records that match an SQL
statement entered in the 'Record Source' property of the form.
The form behaves correctly and displays the records as expected. The
form also displays a 'blank record' after the last record to allow a
user to add a new record. I wish to remove this unwanted and unsightly
'blank record'. To do so, I set 'Allow Additions' to 'No'.
However, changing this property has the catastrophic effect of the
form showing no records at all.
Post the SQL statement.
Please see message 3 of this thread.
> Okay there is a cyclic dependency here. The form's RecordSource depends on a value in the form, and the form doesn't get its value until the RecordSource
is loaded.
This is not a cyclic dependancy. The record source depends on the
value in a text box, but the value in the text box does not depend on
the record source. The value of the text box is dependant on a text
box value within another form (this other form is always open and
always has an appropriate data value).
Particularly, when AllowAdditions is No, it is possible that the form will
have no record at all (as distinct form having the New Record when
AllowAdditions is Yes).
I have tested the form with date values I know for certain contain
records. Again, when 'Allow Additions' is set to 'No' these records
are not displayed.
When you have no records at all in a form - not even
the new record - the entire detail section goes blank, and trying to refer
to one of the non-existent text boxes causes an error.
The text box that is used in the record source is in the header. It is
always present, regardless of whether there are records to display in
the detail section. Interestingly, when 'Allow Additions' is set to
'No', the value of this text box is completely blank. Why should
'Allow Additions' make the text box blank in this case? The value of
the text box relies on the value in another form (as mentioned
earlier) and this shouldn't be affected by 'Allow Additions'.
In addition, there
are bugs in the way Access handles and displays the values in sections other
than the detail section, as discussed in:
http://allenbrowne.com/bug-06.html
So, it seems that the RecordSource's depenency on a value from the form is
preventing it from loading any records at all when AllowAdditions is No.
Can we be sure it is because the record source is dependant on a value
from the form?
There are several workarounds. One would be to programmaticall y assign a
value to the RecordSource of the form after txtDate changes.
Unfortunately, as mentioned earluer, txtDate displays nothing (it is
blank). The controls that work perfectly when 'Allow Additions' is set
to 'Yes' do not work at all when 'Allow Additions' is set to 'No'.
Another would
be to leave AllowAdditions to Yes, and cancel Form_BeforeInse rt event to
prevent any new records.
This would prevent any new records being added, but it would still
display the unsighly 'new blank record'.
BTW, if you really do have a field named "Date", there is a good chance that
Access will get that confused as well. In VBA, Date is a reserved word (for
the system date).
Thank you for the warning. I have changed the name of the field and it
has made no difference to the problem.
With this further information, what do you now suppose the problem is
and what would be a solution?
Thank you for the continued help with this problem.
Regards,
Cro
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message news:<40******* *************** @per-qv1-newsreader-01.iinet.net.au >... Okay there is a cyclic dependency here. The form's RecordSource depends on a
value in the form, and the form doesn't get its value until the RecordSource
is loaded.
Particularly, when AllowAdditions is No, it is possible that the form will
have no record at all (as distinct form having the New Record when
AllowAdditions is Yes). When you have no records at all in a form - not even
the new record - the entire detail section goes blank, and trying to refer
to one of the non-existent text boxes causes an error. In addition, there
are bugs in the way Access handles and displays the values in sections other
than the detail section, as discussed in:
http://allenbrowne.com/bug-06.html
So, it seems that the RecordSource's depenency on a value from the form is
preventing it from loading any records at all when AllowAdditions is No.
There are several workarounds. One would be to programmaticall y assign a
value to the RecordSource of the form after txtDate changes. Another would
be to leave AllowAdditions to Yes, and cancel Form_BeforeInse rt event to
prevent any new records.
BTW, if you really do have a field named "Date", there is a good chance that
Access will get that confused as well. In VBA, Date is a reserved word (for
the system date).
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com...
Thanks for replying. It is nice to know that a developer who "knows
more about Access than any other developer in Australia" is helping
out a developer in England who can't fathom out the side effects of
the 'Allow Additions' form property.
Are you certain you have not set the Data Entry property of the form to Yes as well? That will prevent existing records being loaded.
Data Entry is and always has been set to 'No'.
Alternatively, is anything filtering the form?
Nothing is or ever has been filtering the form.
Or, is there anything in the SQL statement that is depending on a value in the form? Or perhaps a calculated field that could have its data type
misunderstood?
This is my SQL statement:
SELECT tblStaffHours.*
FROM tblStaffHours
WHERE (((Forms!frmSta ffHours!txtDate )=tblStaffHours .Date));
You can see that the SQL statement does rely on a value in the form,
namely a date value. The user can increment and decrement this date
value (as well as jump to today and tomorrow's date) with command
buttons. The 'On Click' event of these command buttons first adjusts
the value within the date text box ('txtDate') and performs a requery
on the form ("DoCmd.Requery "), so that the SQL statement (that is the
record source of the form) is re-invoked.
How would the fact that the SQL statement relies on something in the
form affect its behavior? This is especially confusing as the form
behaves correctly when 'Allow Additions' is set to 'Yes', but the form
behaves very differently (as described in the first post of this
thread) when 'Allow Additions' is set to 'No'.
Incidentally, I have a second form using this exact same concept
(adjusting 'txtDate' to load appropriate records) that works
perfectly. For this second form, I need to be able to add records and
so 'Allow Additions' is set to 'Yes'. This form also fails in the same
way when 'Allow Additions' is set to 'No'.
Thank you for your help with this problem. It is very much
appreciated.
Regards,
Cro
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:<40******* *************** @per-qv1-newsreader-01.iinet.net.au >... Something else is wrong here.
Are you certain you have not set the Data Entry property of the form to Yes as well? That will prevent existing records being loaded.
Alternatively, is anything filtering the form?
Or, is there anything in the SQL statement that is depending on a value in the form? Or perhaps a calculated field that could have its data type
misunderstood?
"Cro" <th*******@hotm ail.com> wrote in message
news:24******** *************** ***@posting.goo gle.com...
> Dear Access Developers,
>
> The 'Allow Additions' property of my form is causing unexpected
> results.
>
> I am developing a form that has its 'Default View' property set to
> 'Continuous Forms' and am displaying records that match an SQL
> statement entered in the 'Record Source' property of the form.
>
> The form behaves correctly and displays the records as expected. The
> form also displays a 'blank record' after the last record to allow a
> user to add a new record. I wish to remove this unwanted and unsightly
> 'blank record'. To do so, I set 'Allow Additions' to 'No'.
>
> However, changing this property has the catastrophic effect of the
> form showing no records at all. By simply adjusting the 'Allow
> Additions' property back to 'Yes', the form behaves correctly once
> more and shows all the expected records (as well as the unsightly
> 'new' record).
>
> I understand that the detail section of a form will be completely
> blank if a) there are no records to display and b) no new records can
> be added. But there definitely are records to display so I am confused
> as to why the records are not being displayed.
>
> Surely my form should still show the expected records?
>
> Do any Access Gurus know what the problem is? Could you be kind enough
> to suggest a solution?
>
> My only idea is to rebuild all of the functionality of my form in a
> report. This wouldn't be ideal as some of the behavior of my form
> wouldn't map well or easily to a report, so any other suggestions
> would be welcomed.
>
> Thank you for your help and expertise,
>
> Cro
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Jim C Nguyen |
last post by:
I have a table with ~2.2 million rows. Sometimes when I do an update
to one single row it will instead update ALL of the rows using the
same update. This happens every one in about 500,000 updates to a
single row.
I am running mysql 4.0.14 in WinXP. I am using PHP to do the update.
I am thinking something in the update itself is causing mysql to do
this. I don't have the exact SQL statement that causes the error
but I do have...
|
by: Eric Anderson Vianet SAO |
last post by:
hello all
When i tried ´pg_dump -v -f dump.dmp dtbtransporte´ I got the error:
pg_dump: restoring data for table tbdmovimento
pg_dump: dumping out the contents of table tbdmovimento
pg_dump: ERROR: unexpected chunk number 8 (expected 0) for toast value 6935693
|
by: Sean |
last post by:
I have a struct that I wrote to test a protocol. The idea I had was
to just declare the elements of the struct in the order in which they
are sent and received as defined by the protocol. However, writing
this struct to a file produces unexpected results.
Here is a test struct I wrote:
struct Tester {
unsigned short first;
unsigned int second;
|
by: Michel Rouzic |
last post by:
I need to determine how long does an addition take and how long does a
multiplication takes. So far I've been trying to use the clock()
function in my programs in order to find out how long it took the CPU
to compute it, the only problem is that I get fairly inconsistent
results, inconsistent enough not to know between two codes which code
runs faster without running each about ten times and making the average
of the reported CPU times.
...
|
by: Martijn Mulder |
last post by:
/*
GraphicsPath.IsVisible() gives unexpected results. I fill a
System.Drawing.Drawing2D.GraphicsPath-object with PointF-structures
that define the unit-square (0,0), (1,0), (1,1) and (0,1). Then I
test 3 different PointF-structures to see if they fall inside the unit-
square and the results are clearly wrong:
Point(-0.2, -0.2) falls inside the unit square... WRONG!!!
Point(0.2, 0.2) falls inside the unit square...
Point(0.7, 0.7) falls...
| | |
by: chris |
last post by:
I'm trying to create the following:
When a user opens a form, if the form's Sub-form has a record, then
they have to click a command button in order to add a new record. If
the Sub-form does not have a record, then a new record in that sub-
form is shown. Actually it doesn't even matter if a new record is
shown. Thye can still click the command button to add a record. I
just don't know how to identify that sub-form in the On Click...
|
by: paquer |
last post by:
I want users to be able to set the Allow Additions property to 'True'
via a command button when required. (The command also adds data to the
subform) If they skip the command, they skip the data transfer. Hence
I want to set the Allow Additions property via a command button.
I set up the command button with the following code, but I keep
getting an error: Method or Data Member not found (Debug highlights
the allow additions section.
...
|
by: blakerrr |
last post by:
Hi All,
I have a subform, which needs to allow for additions. When I set the "Allow Additions" property to Yes, the form still doesn't allow me to add anything.
Am I missing something here???
Thanks.
|
by: bintom |
last post by:
I ran the following simple code in C++ and got unexpected results:
float f = 139.4;
cout << f;
Output:
139.399994;
|
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: 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.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
| | |
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: 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: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| | |
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...
| |
