[AccessD] Connection string to web mdb

Hi Steve

This is not just like that. You could create a VPN connection but in most practical scenarios not on the fly. Firewalls need manual adjustment.

And even if you could, connection to an mdb via the internet is not recommended, indeed not for writing. It may work but it will break sooner or later and you'll have a corrupted backend.

/gustav

>>> scapistrant at symphonyinfo.com 02-07-2008 16:14 >>>
Oh...Well, that explains it clearly enough. Thank you!

I can deal with the drive mapping method, which works fine for MY machine,
but in my ideal world I want this tool to be distributable, which means I
won't know the user's current mapping assignments.  I can write code that
establishes a drive mapping (in this case, to the website) on the fly to a
specific letter, but I'm not sure how the code can assess which drive
letters are available.  I'll do some research, but if anyone has
ready-to-eat advice, I would appreciate it.

Thanks again, Gustav.

Steve Capistrant

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, July 02, 2008 8:53 AM
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] Connection string to web mdb

Hi Steve

You can't, that's why you can't find anything.

You need a drive letter or a UNC path - or you must download/upload the
file.

/gustav

>>> scapistrant at symphonyinfo.com 02-07-2008 15:26 >>>
Hello,

Does anyone have any experience in making a live connection from local MDB
to a web-server MDB?  I've looked at all the connection string examples in
AccessD archives, and at http://www.connectionstrings.com, and similar
websites.  Most seem focused on connecting to an MDB on the LAN.

-----------
I have successfully connected using a "local mdb to a web-based SQL Server"
setup:

Step 1: Run a pass-through query to open/refresh the connection.  The
query's connection string is:

ODBC;Description=DescripOfMyAccessDatabaseOnWebServer;DRIVER=SQL
Server;SERVER=70.90.79.73;UID=MyLoginName;PWD=MyPassword;DATABASE=NameOfMyDa
tabaseInSQLServerOnWebServer

Step 2:  Each table link has a connection string of:

ODBC;Description=DescripOfMyAccessDbOnRemoteWebServer;DRIVER=SQL
Server;SERVER=70.90.79.73;UID=MyLoginName;APP=MicrosoftR
Access;WSID=NameOfMyLocalComputer;DATABASE=
NameOfMyDatabaseInSQLServerOnWebServer;TABLE=MyTableName
-----

The only code I have found for a "local mdb to web-based mdb" setup is:

"Provider=MS Remote; Remote Server=http://Your-Remote-Server-IP; Remote
Provider=Microsoft.Jet.OLEDB.4.0; Data
Source=c:\App1\Your_Database_Name.mdb" 

But I can't make it work.  I also read that this approach is no longer
supported by Microsoft, but is supposed to still work, at least for now.
Does it require creating a DSN?  Where am I going wrong?
--------

Any tips? Thank you!

Steve Capistrant
Email: s.t.capistrant at gmail.com