J
jbiggs via AccessMonster.com
We currently have an Access 2003 DB locally which stores client information
for internal use. We have another DB sitting out on a website which collects
leads. We then have an automated procedure which ftp's to the site,
downloads the DB and uploads a blank DB. The information is then imported
into the main DB using an import tool in Access.
This is obviously not an ideal situation and there are often problems if
someone is trying to input new leads while the ftp is happening. Is there a
more efficient way to do this? ADP or linking to the internet DB as a
temporary table?
We may be switching over to a PHP/mySQL solution in the near future if that
in any way affects someones response.
for internal use. We have another DB sitting out on a website which collects
leads. We then have an automated procedure which ftp's to the site,
downloads the DB and uploads a blank DB. The information is then imported
into the main DB using an import tool in Access.
This is obviously not an ideal situation and there are often problems if
someone is trying to input new leads while the ftp is happening. Is there a
more efficient way to do this? ADP or linking to the internet DB as a
temporary table?
We may be switching over to a PHP/mySQL solution in the near future if that
in any way affects someones response.