I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms
with ODBC linked tables. In one form, the user needs to be able to check a
box to select one or more records. This is accomplished with a local table
containing two fields: the primary key value of the SQL table and a boolean
field used for the check box.
Since the local table used to contain the boolean field is local to the MDB
file, the result is a heterogeneous join in the underlying form query, which
degrades performance. I would like to have the entire query be based on back
end SQL data. However, each user needs to be able to make a unique set of
selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an
additional field for machine name; create a view of the main table joined to
the selections table; link the view to the front end; and base the form on
the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be
appreciated.
Thanks,
Neil 18 1975
Relying on machine names may be difficult, since if the machine name
changes, your code will not work (not that it is very frequent, but it
happens). One technique that I've seen people use is to have a local MDB
table itself for making the selections. You can then form a comma-separated
list of IDs that is then sent to a backend procedure. In this procedure, you
can conver the comma-separated values into a temp table (using the
techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do
the join with the actual table to show the results back.
--
HTH,
SriSamp
Email: sr*****@gmail.c om
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message
news:1L******** ********@newsre ad1.news.pas.ea rthlink.net... I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additional field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciated.
Thanks,
Neil
The machine name changing isn't an issue, since these selections are
temporary -- maybe a few hours or overnight at the most. They're not
permanent entities.
Also, if I use a temporary table, I'm not sure how I would bring that into
the front end except through a pass-through query. In that case, it would be
read-only.
Thus, I think it's best that I work with a view that joins the two table or
some other method that allows me to link it via ODBC. I'm a little leary
about the approach I outlined in my message since it means that the view
will have X records x Y machines, which would make it very large. Granted,
it would only return the records for the current machine. Still, it seems
that there would be a large number of records initially dealt with.
Thanks,
Neil
"SriSamp" <ss******@sct.c o.in> wrote in message
news:eu******** ******@TK2MSFTN GP14.phx.gbl... Relying on machine names may be difficult, since if the machine name changes, your code will not work (not that it is very frequent, but it happens). One technique that I've seen people use is to have a local MDB table itself for making the selections. You can then form a comma-separated list of IDs that is then sent to a backend procedure. In this procedure, you can conver the comma-separated values into a temp table (using the techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do the join with the actual table to show the results back. -- HTH, SriSamp Email: sr*****@gmail.c om Blog: http://blogs.sqlxml.org/srinivassampath URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message news:1L******** ********@newsre ad1.news.pas.ea rthlink.net...I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additional field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciated.
Thanks,
Neil
You can create a temporary table in Access only by using Docmd.Runsql
"CREATE TABLE #...", and then using the table as a recordsource for a
form (just be sure to assign the recordsource after the creation of the
table). If you create a primary key in the table, you will be able to
edit it in your forms.
The temporary table will be dropped using a Docmd.Runsql "DROP TABLE
#.."-statement or when the connection from the front-end is closed.
In the procedure, you can then use the temporary table in the queries.
Neil wrote: The machine name changing isn't an issue, since these selections are temporary -- maybe a few hours or overnight at the most. They're not permanent entities.
Also, if I use a temporary table, I'm not sure how I would bring that into the front end except through a pass-through query. In that case, it would be read-only.
Thus, I think it's best that I work with a view that joins the two table or some other method that allows me to link it via ODBC. I'm a little leary about the approach I outlined in my message since it means that the view will have X records x Y machines, which would make it very large. Granted, it would only return the records for the current machine. Still, it seems that there would be a large number of records initially dealt with.
Thanks,
Neil
"SriSamp" <ss******@sct.c o.in> wrote in message news:eu******** ******@TK2MSFTN GP14.phx.gbl...
Relying on machine names may be difficult, since if the machine name changes, your code will not work (not that it is very frequent, but it happens). One technique that I've seen people use is to have a local MDB table itself for making the selections. You can then form a comma-separated list of IDs that is then sent to a backend procedure. In this procedure, you can conver the comma-separated values into a temp table (using the techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do the join with the actual table to show the results back. -- HTH, SriSamp Email: sr*****@gmail.c om Blog: http://blogs.sqlxml.org/srinivassampath URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message news:1L****** **********@news read1.news.pas. earthlink.net.. .
I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additional field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciate d.
Thanks,
Neil
The strategy I've arrived at is to have a table of working sets, and have the
table of selections include the working set key. When the user starts the
task, the program first makes a new working set record, and thus gets a new
unique ID for the set of selection records.
With this design, you can keep treating working sets as dynamic by deleting
them after use (and have a garbage collection process to empty out old ones
that failed to get deleted) or allow the user to name them, keep them around,
and refer to them again later.
On Fri, 14 Oct 2005 08:11:41 GMT, "Neil" <no****@nospam. net> wrote: I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additional field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciated.
Thanks,
Neil
I never had much luck with that. Access uses more than one connection to do
its work, and doesn't hold connections open indefinitely, so it's not clear
whether, after creating a temp table, Access will be able to find it later.
You also can't bind a for to a query involving a temp table and have it be
editable because you have to use a pass-though query.
On Fri, 14 Oct 2005 14:35:25 +0200, "Ol!v!é"
<stevenlangenak en-at-@gmail-dot-.com> wrote: You can create a temporary table in Access only by using Docmd.Runsql "CREATE TABLE #...", and then using the table as a recordsource for a form (just be sure to assign the recordsource after the creation of the table). If you create a primary key in the table, you will be able to edit it in your forms. The temporary table will be dropped using a Docmd.Runsql "DROP TABLE #.."-statement or when the connection from the front-end is closed.
In the procedure, you can then use the temporary table in the queries.
Neil wrote: The machine name changing isn't an issue, since these selections are temporary -- maybe a few hours or overnight at the most. They're not permanent entities.
Also, if I use a temporary table, I'm not sure how I would bring that into the front end except through a pass-through query. In that case, it would be read-only.
Thus, I think it's best that I work with a view that joins the two table or some other method that allows me to link it via ODBC. I'm a little leary about the approach I outlined in my message since it means that the view will have X records x Y machines, which would make it very large. Granted, it would only return the records for the current machine. Still, it seems that there would be a large number of records initially dealt with.
Thanks,
Neil
"SriSamp" <ss******@sct.c o.in> wrote in message news:eu******** ******@TK2MSFTN GP14.phx.gbl...
Relying on machine names may be difficult, since if the machine name changes, your code will not work (not that it is very frequent, but it happens). One technique that I've seen people use is to have a local MDB table itself for making the selections. You can then form a comma-separated list of IDs that is then sent to a backend procedure. In this procedure, you can conver the comma-separated values into a temp table (using the techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do the join with the actual table to show the results back. -- HTH, SriSamp Email: sr*****@gmail.c om Blog: http://blogs.sqlxml.org/srinivassampath URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message news:1L***** ***********@new sread1.news.pas .earthlink.net. ..
I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containin g two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additiona l field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciated .
Thanks,
Neil
On Fri, 14 Oct 2005 08:11:41 GMT, "Neil" <no****@nospam. net> wrote: I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
By the way - if you can ditch Access 2000 for 2002 or 2003 - do it now.
Access 2000 has far more bugs and quirks with ODBC usage that can waste your
time and get you into trouble.
The problem is that I won't be able to edit the data if I access it through
a pass-through query. The table needs to be linked to the MDB in order for
it to be edited.
What would be best would be if it were possible to have a view that is
linked to the front end, but which can be customized to return the records
only for the particular user.
Thanks,
Neil
""Ol!v!é"" <stevenlangenak en-at-@gmail-dot-.com> wrote in message
news:11******** *******@seven.k ulnet.kuleuven. ac.be... You can create a temporary table in Access only by using Docmd.Runsql "CREATE TABLE #...", and then using the table as a recordsource for a form (just be sure to assign the recordsource after the creation of the table). If you create a primary key in the table, you will be able to edit it in your forms. The temporary table will be dropped using a Docmd.Runsql "DROP TABLE #.."-statement or when the connection from the front-end is closed.
In the procedure, you can then use the temporary table in the queries.
Neil wrote: The machine name changing isn't an issue, since these selections are temporary -- maybe a few hours or overnight at the most. They're not permanent entities.
Also, if I use a temporary table, I'm not sure how I would bring that into the front end except through a pass-through query. In that case, it would be read-only.
Thus, I think it's best that I work with a view that joins the two table or some other method that allows me to link it via ODBC. I'm a little leary about the approach I outlined in my message since it means that the view will have X records x Y machines, which would make it very large. Granted, it would only return the records for the current machine. Still, it seems that there would be a large number of records initially dealt with.
Thanks,
Neil
"SriSamp" <ss******@sct.c o.in> wrote in message news:eu******** ******@TK2MSFTN GP14.phx.gbl...
Relying on machine names may be difficult, since if the machine name changes, your code will not work (not that it is very frequent, but it happens). One technique that I've seen people use is to have a local MDB table itself for making the selections. You can then form a comma-separated list of IDs that is then sent to a backend procedure. In this procedure, you can conver the comma-separated values into a temp table (using the techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do the join with the actual table to show the results back. -- HTH, SriSamp Email: sr*****@gmail.c om Blog: http://blogs.sqlxml.org/srinivassampath URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message news:1L***** ***********@new sread1.news.pas .earthlink.net. ..
I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additiona l field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName ='MyMachine'".
However, I wonder if there's a better approach. Any ideas would be appreciated .
Thanks,
Neil
Right. So it seems that my original idea of just having a view that returns
all records and then use the machine name as a criterion in the recordsource
query is the only way to go. Unless you have another idea? See any problems
with that approach?
Thanks,
Neil
"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:6n******** *************** *********@4ax.c om... I never had much luck with that. Access uses more than one connection to do its work, and doesn't hold connections open indefinitely, so it's not clear whether, after creating a temp table, Access will be able to find it later. You also can't bind a for to a query involving a temp table and have it be editable because you have to use a pass-though query.
On Fri, 14 Oct 2005 14:35:25 +0200, "Ol!v!é" <stevenlangenak en-at-@gmail-dot-.com> wrote:
You can create a temporary table in Access only by using Docmd.Runsql "CREATE TABLE #...", and then using the table as a recordsource for a form (just be sure to assign the recordsource after the creation of the table). If you create a primary key in the table, you will be able to edit it in your forms. The temporary table will be dropped using a Docmd.Runsql "DROP TABLE #.."-statement or when the connection from the front-end is closed.
In the procedure, you can then use the temporary table in the queries.
Neil wrote: The machine name changing isn't an issue, since these selections are temporary -- maybe a few hours or overnight at the most. They're not permanent entities.
Also, if I use a temporary table, I'm not sure how I would bring that into the front end except through a pass-through query. In that case, it would be read-only.
Thus, I think it's best that I work with a view that joins the two table or some other method that allows me to link it via ODBC. I'm a little leary about the approach I outlined in my message since it means that the view will have X records x Y machines, which would make it very large. Granted, it would only return the records for the current machine. Still, it seems that there would be a large number of records initially dealt with.
Thanks,
Neil
"SriSamp" <ss******@sct.c o.in> wrote in message news:eu******** ******@TK2MSFTN GP14.phx.gbl...
Relying on machine names may be difficult, since if the machine name changes, your code will not work (not that it is very frequent, but it happens). One technique that I've seen people use is to have a local MDB table itself for making the selections. You can then form a comma-separated list of IDs that is then sent to a backend procedure. In this procedure, you can conver the comma-separated values into a temp table (using the techniques in: http://www.algonet.se/~sommar/arrays-in-sql.html) and then do the join with the actual table to show the results back. -- HTH, SriSamp Email: sr*****@gmail.c om Blog: http://blogs.sqlxml.org/srinivassampath URL: http://www32.brinkster.com/srisamp
"Neil" <no****@nospam. net> wrote in message news:1L**** ************@ne wsread1.news.pa s.earthlink.net ...
>I am using SQL 7 with an MS Access 2000 MDB front end, using bound >forms >with ODBC linked tables. In one form, the user needs to be able to >check a >box to select one or more records. This is accomplished with a local >table >containi ng two fields: the primary key value of the SQL table and a >boolean field used for the check box. > >Since the local table used to contain the boolean field is local to the >MDB file, the result is a heterogeneous join in the underlying form >query, which degrades performance. I would like to have the entire >query >be based on back end SQL data. However, each user needs to be able to >make a unique set of selections, without other users' selections >affectin g theirs. > >An idea I have is to port the selections table to the back end with an >addition al field for machine name; create a view of the main table >joined >to the selections table; link the view to the front end; and base the >form on the SQL: "Select * From MyView Where MachineName='My Machine'". > >However, I wonder if there's a better approach. Any ideas would be >appreciate d. > >Thanks, > >Neil >
That sounds fine, and is similar to what I mentioned (working set key would
be machine name). When you used these, were they linked to an MDB or were
they just back end processes? I need to be able to use this in a bound form
approach, where the selection check box on the form is bound to the
selection table. Thus, the recordsource for the form needs to just return
the records pertaining to a particular working set key. How did you
accomplish that?
Thanks,
Neil
"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:ac******** *************** *********@4ax.c om... The strategy I've arrived at is to have a table of working sets, and have the table of selections include the working set key. When the user starts the task, the program first makes a new working set record, and thus gets a new unique ID for the set of selection records.
With this design, you can keep treating working sets as dynamic by deleting them after use (and have a garbage collection process to empty out old ones that failed to get deleted) or allow the user to name them, keep them around, and refer to them again later.
On Fri, 14 Oct 2005 08:11:41 GMT, "Neil" <no****@nospam. net> wrote:
I am using SQL 7 with an MS Access 2000 MDB front end, using bound forms with ODBC linked tables. In one form, the user needs to be able to check a box to select one or more records. This is accomplished with a local table containing two fields: the primary key value of the SQL table and a boolean field used for the check box.
Since the local table used to contain the boolean field is local to the MDB file, the result is a heterogeneous join in the underlying form query, which degrades performance. I would like to have the entire query be based on back end SQL data. However, each user needs to be able to make a unique set of selections, without other users' selections affecting theirs.
An idea I have is to port the selections table to the back end with an additional field for machine name; create a view of the main table joined to the selections table; link the view to the front end; and base the form on the SQL: "Select * From MyView Where MachineName='My Machine'".
However, I wonder if there's a better approach. Any ideas would be appreciated .
Thanks,
Neil This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: JL |
last post by:
Does anyone have any ideas on this please?
I don't know how to evaluate the no-blank selections against each other from
a form as follows: .
I have a form with 6 dropdown fields, each containing a selection of 30
options (the 30 options are the same for each dropdown list).
The user needs to select 'one of the 30 options' from each...
|
by: Colleyville Alan |
last post by:
I have been working on a project that uses MS Access to get mutual fund
performance and write it to a spreadsheet in a formatted manner. The user
inputs the company name, the database looks at the company's 401k fund
holdings and extracts the performance info and benchmark info for them. It
writes out the information to a spreadsheet...
|
by: Terri |
last post by:
I have a form with a multi-select combo. I dynamically build a SELECT
statement, open a report, and set the recordsource to my dynamic SELECT
statement. I count the records returned in the report by setting a text box
to =Count(*). This works fine.
Now I want to count the unique records in my report. I can dynamically
create a SELECT...
|
by: Alpha |
last post by:
Hi,
I'm working on a Windows applicaton with VS 2003 on windows 2000. I have a
listbox that I have binded to a dataset table, "source" which has 3 columns.
I would like to display 2 of those columns, "scode" and "sname", as 1 column
(if not possible then 2 columns will be fine) in the listbox. Can the
listbox display 2 columns information...
|
by: John Hoge |
last post by:
I'm looking for that elusive .net time saving magic.
I have an application that presents a list of items which the user can
select from. A CheckBoxList works great for that, but I want to query
a database based on their selections.
I'm forced to dynamically building a SQL statement in a method I could
have done easily in classic ASP:
...
| |
by: nescio |
last post by:
hello,
i have an array and i don't know the content of it, but i want only unique
values.
in php there is a function to do this, but how must i do this in javascript?
i have tried a lot and it is driving me nuts
|
by: Yvonne |
last post by:
We have a Contacts database which categorises our Contacts by three
categories eg Country, Language and Skills.
It has a combo box ( not bound) which is populated from a union query
that gets its values from the 3 category fields. At present the
after-update event on the combo box generates a report which selects
those contacts matching the...
|
by: jmartmem |
last post by:
Greetings,
I have an ASP page with a 5x5 table embedded inside an Insert Record Form. This table contains several fields (mostly drop down list menus) and is used for corporate timekeeping (users record their daily hours by making selections from the list menus).
My challenge is to figure out how the user can complete all rows of the table...
|
by: andersond |
last post by:
I have a webpage that uses visible and hidden tables to create the effect of going from screen to screen. Because a user might want to go back and change previous selections I have a "previous page" button that goes back to a table that has been made hidden. Text fields retain their values; but, option buttons do not. I am having problems...
|
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...
|
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...
| |
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. ...
|
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...
|
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...
|
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...
|
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...
|
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...
| |
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...
| |