Export / Import data to update main database or utilise alternativ

Hi,
At the moment we have a standalone, split database, deployed via the Access
Developer Extension.

The issue:
We are just about to launch into an expansion programme which will bring the
introduction of a number of new franchised companies and we want to deploy
the database as part of the franchise. The parent company will own all the
data and therefore we want to make sure that they we have access to the
database or get regular updates from the franchisee.

The data volumes are not huge.
The franchisee’s will not be networked to the parent company (or each other).

I’m looking for recommendations here regarding the set up of the DB.
My initial thoughts were just to export the data from each franchisee on a
weekly basis. Email this to the parent company and then import to the master
database.

My only concern would be how to make the data secure during the email
process – preferably automating the encryption / password control on export
from the franchisee and then the same on the import i.e. automating the
decryption / password.

If the email option is not viable / recommended can you propose
alternatives….We need to keep costs realistic but at the same time provide a
solution that is viable and secure.

Your input is appreciated.

Thanks in advance.

Kirk

Consider FTP as the transport medium. You can write VBA code that will do
the FTP process to secure server, using third-party FTP objects.

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"IKMD66" wrote in message
...
Hi,
At the moment we have a standalone, split database, deployed via the
Access
Developer Extension.

The issue:
We are just about to launch into an expansion programme which will bring
the
introduction of a number of new franchised companies and we want to deploy
the database as part of the franchise. The parent company will own all the
data and therefore we want to make sure that they we have access to the
database or get regular updates from the franchisee.

The data volumes are not huge.
The franchisee's will not be networked to the parent company (or each
other).

I'm looking for recommendations here regarding the set up of the DB.
My initial thoughts were just to export the data from each franchisee on a
weekly basis. Email this to the parent company and then import to the
master
database.

My only concern would be how to make the data secure during the email
process - preferably automating the encryption / password control on
export
from the franchisee and then the same on the import i.e. automating the
decryption / password.

If the email option is not viable / recommended can you propose
alternatives..We need to keep costs realistic but at the same time provide
a
solution that is viable and secure.

Your input is appreciated.

Thanks in advance.

Kirk

Ken,

Thanks for the response. If FTP is the way to go do you have any sample
code, or can you point me in the right direction....ideally I want to
automate the export on close of the franchisee DB, checking that the compute
has connection to the internet. On the import I would prefer to poll for
files, however it could be done explicitly by the user.

Again any further information / assistance is appreciated.

Regards,
Kirk

"Ken Snell [MVP]" wrote:

Consider FTP as the transport medium. You can write VBA code that will do
the FTP process to secure server, using third-party FTP objects.

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"IKMD66" wrote in message
...
Hi,
At the moment we have a standalone, split database, deployed via the
Access
Developer Extension.

The issue:
We are just about to launch into an expansion programme which will bring
the
introduction of a number of new franchised companies and we want to deploy
the database as part of the franchise. The parent company will own all the
data and therefore we want to make sure that they we have access to the
database or get regular updates from the franchisee.

The data volumes are not huge.
The franchisee's will not be networked to the parent company (or each
other).

I'm looking for recommendations here regarding the set up of the DB.
My initial thoughts were just to export the data from each franchisee on a
weekly basis. Email this to the parent company and then import to the
master
database.

My only concern would be how to make the data secure during the email
process - preferably automating the encryption / password control on
export
from the franchisee and then the same on the import i.e. automating the
decryption / password.

If the email option is not viable / recommended can you propose
alternatives..We need to keep costs realistic but at the same time provide
a
solution that is viable and secure.

Your input is appreciated.

Thanks in advance.

Kirk

I have used this third-party control -- there is sample code at that site,
too:
http://www.chilkatsoft.com/ChilkatFtp.asp

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"IKMD66" wrote in message
...
Ken,

Thanks for the response. If FTP is the way to go do you have any sample
code, or can you point me in the right direction....ideally I want to
automate the export on close of the franchisee DB, checking that the
compute
has connection to the internet. On the import I would prefer to poll for
files, however it could be done explicitly by the user.

Again any further information / assistance is appreciated.

Regards,
Kirk

"Ken Snell [MVP]" wrote:

Consider FTP as the transport medium. You can write VBA code that will do
the FTP process to secure server, using third-party FTP objects.

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"IKMD66" wrote in message
...
Hi,
At the moment we have a standalone, split database, deployed via the
Access
Developer Extension.

The issue:
We are just about to launch into an expansion programme which will
bring
the
introduction of a number of new franchised companies and we want to
deploy
the database as part of the franchise. The parent company will own all
the
data and therefore we want to make sure that they we have access to the
database or get regular updates from the franchisee.

The data volumes are not huge.
The franchisee's will not be networked to the parent company (or each
other).

I'm looking for recommendations here regarding the set up of the DB.
My initial thoughts were just to export the data from each franchisee
on a
weekly basis. Email this to the parent company and then import to the
master
database.

My only concern would be how to make the data secure during the email
process - preferably automating the encryption / password control on
export
from the franchisee and then the same on the import i.e. automating the
decryption / password.

If the email option is not viable / recommended can you propose
alternatives..We need to keep costs realistic but at the same time
provide
a
solution that is viable and secure.

Your input is appreciated.

Thanks in advance.

Kirk