Drew Wutka
DWUTKA at marlow.com
Tue Oct 28 16:20:41 CST 2003
Yes, but not the way you are thinking. The first sub-contract job I did for my sister was for a company that was hosted by a hosting company that 'supported' Access. It also supported ActiveX .dll's. So I wrote a .dll to interact with the database, the .dll used ADO to connect to the db, and for the path to the db, it just used the path to the .dll. Therefore, I uploaded the .dll and the db to the same folder. Worked like a charm. In most occasions, I am writing stuff for IIS servers I have DIRECT access too. In those cases, I actually put the .mdb in a location that is NOT visible to the web, then I hard code the actual path into the .dll. Thus, the asp pages can interact with the .dll, but the .mdb is never directly visible to the user. Drew -----Original Message----- From: Steven W. Erbach [mailto:serbach at new.rr.com] Sent: Tuesday, October 28, 2003 4:07 PM To: accessd at databaseadvisors.com Subject: [AccessD] Access database on the Internet Dear Group, Have any of you uploaded an Access back end to a web server capable of "handling" Access? I'm a bit confused by my web host's claim to support unlimited Access databases. Are we talking uploading the back end, say, and establishing an ODBC link to it sort of like an ODBC link to a SQL Server database? Regards, Steve Erbach Scientific Marketing Neenah, WI _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com