MS Access Desktop & Online.. Possible?

  • Thread starter Thread starter Mike Wilson
  • Start date Start date
there is no such thing as a specialist in Access / JET.

People don't specialize in Access / JET.

Access / JET is but a speed bump on the way to SQL Server; if you
don't believe that then you've been conned into buying Oracle or
soemthing.


How can Oracle and IBM be competitive when neither one of them offers
an Olap component?
www.olapreport.com - Microsoft won the database war because they won
the OLAP war



and Accesss / JET is but a speed bump.

I'll find those silly articiles-- and I'll find the original verbage.
 
Searching under this KB Article, combined with the word 'JET'
I was looking for a prior version of this KB Article.

You see-- I don't beleive that MIcrosoft has the AUTHORITY to rewrite
history.
If MIcrosoft says that JET IS NOT RECCOMENDED FOR IIS they do not have
my permissions to change their reccomendations five years later.

What do they do, read strategy off of a cracker-jax box?

Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases
Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases
Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases
Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases
Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases

Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases, there are
several advantages to using OLE DB versus ODBC for Access database
connections. One of the benefits of using OLE DB connections is the
ability to connect to databases without the need to create a user or
system DSN on the Web server. Other advantages include the ability to
call a thread-safe version of Visual Basic for Applications, and
increased stability.

http://www.kbalertz.com/264691/Creating.Connection.String.Access.Database.aspx
http://www.kbalertz.com/838306/responding.Microsoft.Access.applications.aspx



http://support.propelhosting.com/asp_odbc.htm


--IMPORTANT ODBC INFO--

The "Microsoft Access ODBC Driver" is no longer supported by
Microsoft. As such, Windows 2003 has issues with this particular
driver. We have modified Hsphere so that users can no longer setup
System DSNs (ODBC) for Access. We have updated this page on
information on the proper connection string to use for connecting to
Access databases.

As such, we will also be removing the Microsoft Access ODBC Driver.

YOU CAN STILL CONNECT TO ACCESS DATABASES, YOU MUST MODIFY YOUR
CONNECTION STRING TO USE THE "Microsoft.Jet.OLEDB.4.0" DRIVER!!!!!!

-----

Here is an example connection string:

oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=c:somepathmyDb.mdb;User Id=admin;Password="


If you are interested in reading about this issue, refer to the
Microsoft Knowledgebase article here:

http://support.microsoft.com/defaul...KB;EN-US;299973

The ODBC driver was written years before IIS was developed therefore
the two do not work reliably together.

Please see the following for more information.

"299973.KB.EN-US ACC2000: Using Microsoft Jet with IIS"

found at: http://support.microsoft.com/defaul...KB;EN-US;299973

We strongly recommend that you use the Microsoft OLEDB Provider for
JET if you must use Access in an ASP application. Please keep in mind
that there are many other issues that occur when using Access in this
environment and even if you move to the OLEDB Provider you may still
experience errors.




http://p2p.wrox.com/topic.asp?TOPIC_ID=18183
 
Searching under this KB Article, combined with the word 'JET'
I was looking for a prior version of this KB Article.

You see-- I don't beleive that MIcrosoft has the AUTHORITY to rewrite
history.
If MIcrosoft says that JET IS NOT RECCOMENDED FOR IIS they do not have
my permissions to change their believe five years late.

What do they do, read strategy off of a cracker-jax box?

Although Microsoft does not recommend that you use Internet
Information Server (IIS) to connect to Access databases, there are
several advantages to using OLE DB versus ODBC for Access database
connections. One of the benefits of using OLE DB connections is the
ability to connect to databases without the need to create a user or
system DSN on the Web server. Other advantages include the ability to
call a thread-safe version of Visual Basic for Applications, and
increased stability.

http://www.kbalertz.com/264691/Creating.Connection.String.Access.Database.aspx
http://www.kbalertz.com/838306/responding.Microsoft.Access.applications.aspx



http://support.propelhosting.com/asp_odbc.htm


--IMPORTANT ODBC INFO--

The "Microsoft Access ODBC Driver" is no longer supported by
Microsoft. As such, Windows 2003 has issues with this particular
driver. We have modified Hsphere so that users can no longer setup
System DSNs (ODBC) for Access. We have updated this page on
information on the proper connection string to use for connecting to
Access databases.

As such, we will also be removing the Microsoft Access ODBC Driver.

YOU CAN STILL CONNECT TO ACCESS DATABASES, YOU MUST MODIFY YOUR
CONNECTION STRING TO USE THE "Microsoft.Jet.OLEDB.4.0" DRIVER!!!!!!

-----

Here is an example connection string:

oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=c:somepathmyDb.mdb;User Id=admin;Password="


If you are interested in reading about this issue, refer to the
Microsoft Knowledgebase article here:

http://support.microsoft.com/defaul...KB;EN-US;299973

The ODBC driver was written years before IIS was developed therefore
the two do not work reliably together.

Please see the following for more information.

"299973.KB.EN-US ACC2000: Using Microsoft Jet with IIS"

found at: http://support.microsoft.com/defaul...KB;EN-US;299973

We strongly recommend that you use the Microsoft OLEDB Provider for
JET if you must use Access in an ASP application. Please keep in mind
that there are many other issues that occur when using Access in this
environment and even if you move to the OLEDB Provider you may still
experience errors.




http://p2p.wrox.com/topic.asp?TOPIC_ID=18183
 
Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


Tom Wickerath said:
CORRECTION

access is usable

Access MDB sucks balls

I use Access ADP across the internet / vpn / wireless / wan _ALL_ the
friggin time
Click to expand...
 
if you have data in an Access Databae, you first need to move it to SQL
Server before using a webpage to get the data out of a datbaase
 
CORRECTION

access is usable

Access MDB sucks balls

I use Access ADP across the internet / vpn / wireless / wan _ALL_ the
friggin time
 
Back
Top