Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: ocean10000
I would prefer to not have more than one copy of the DB floating around, for a number of practical reasons.
I retrieve data using ASP. I would like mysiteB to connect to the database but am not sure if it possible for an ASP page to connect to a database on another site/server. I could put a script on mysiteA where the DB is and use Include to display the results on mysite B but is would be easier, I think, if there were a connection string that would allow this.
Problem is I can't find the syntax for setting a path. Current mysiteA string is:
strDB=server.MapPath("\") & "\database\datastuff.mdb"
mysiteB needs to connect to that file at [mysiteA.com...]
Anyone know the proper path format? I don't believe Mappath is correct to use here. Can't find any examples.
hmmm, when you say site/server, do you mean site or server? :) If website A and website B are both hosted on the same server, I believe this could be solved - the matter was discussed 3 weeks ago here [webmasterworld.com].
If you're using different servers, It's going to be more difficult. I think (but I'm not 100% sure) the only alternatives you have are to set up a webservice on site A and feed that to your other sites OR to switch to another database.
edit: I checked out the able-consulting.com page and found
They have a couple more solutions on how to connect to a remote Access database.
I looked briefly at the thread and checked out the page that you noted. Looks I might have to use ADO with a remote ASP page. I'm not clear yet on the connection string to use but I'll play with it until I get totally confused.
Not sure if this will work, it shouldn't 'cause of server security but give it a shot.
P.S. Don't forget to take out the maybe and the asterisk. ;)
Access has severe multi-thread issues being accessed from http requests and CGI processing.
My suggestion is to bite the bullet, and upgrade to MS-SQL, if you are going to use online CGI/ASP for a commercial website environment...
Access does ok for low volume multi threading, but once you hit a specific activity level, the .mdb can get corrupted if you have it set at anything more open, than "read only"..