----
Stephen US Operations Staff member Oct 12, 2005 #2 Please use DSN-less, using a DNS not only adds a 20% or so increase in load times, but also has an additional point of failure and problems in the ODBC layer,and then in the application pool
Please use DSN-less, using a DNS not only adds a 20% or so increase in load times, but also has an additional point of failure and problems in the ODBC layer,and then in the application pool
Y Yash Bass Oct 12, 2005 #3 Also, please do not use the ODBC driver. Use a DSN-less JET OLEDB connection. Access ODBC is problem ridden and is no longer supported by MS
Also, please do not use the ODBC driver. Use a DSN-less JET OLEDB connection. Access ODBC is problem ridden and is no longer supported by MS
S sonata Perch Oct 12, 2005 #4 Yash said: Also, please do not use the ODBC driver. Use a DSN-less JET OLEDB connection. Access ODBC is problem ridden and is no longer supported by MS Click to expand... Is this something specific to Access, or across the board? Inquiring minds want to know.
Yash said: Also, please do not use the ODBC driver. Use a DSN-less JET OLEDB connection. Access ODBC is problem ridden and is no longer supported by MS Click to expand... Is this something specific to Access, or across the board? Inquiring minds want to know.
Stephen US Operations Staff member Oct 12, 2005 #5 Directly using JET is always best, but SQL has other methods like a built in library for accessing SQL, so basically, just Access+ASP.
Directly using JET is always best, but SQL has other methods like a built in library for accessing SQL, so basically, just Access+ASP.
