Question about distributing a backend database 
Author Message
 Question about distributing a backend database

Hi everybody,

I hope you can help me in a problem that's getting me crazy.

I have divided my database, creating a back end copy containing the tables
and a front end copy with all the queries, forms, reports, etc..
Now I have to send to 18 managers all around my country (Italy) both the
databases and they must send me back every week the back end copy where they
have registered all the sales in their areas. To avoid that they send me all
the tables, I thought to divide once again the back end database to separate
the sales table from the other tables of my database. So I've figured out
the following situation:
a.    the main database (sales.db), containing the engine of the
application;
b.    the first back end db (tables.db), with all the tables but the sales;
c.    a second back end db (area_sales.db), with the sales of every area.

But... never say never: I've found out that when I've divided the area_sales
form the tables I've lost all the relations between the tables and I can't
do anything because of the relational integrity rules. So I had to put the
area sales back into the tables database and receive all the tables each and
every week.

Is there anybody that can help me?

Thank you for your support, I hope that someday I will repay somehow.

Riccardo Marcante

{*filter*}s like us...



Sat, 23 Sep 2000 03:00:00 GMT  
 Question about distributing a backend database

I would suggest you have them use SendObject to email the sales table to you.

Douglas Hansknecht

Quote:

> Hi everybody,

> I hope you can help me in a problem that's getting me crazy.

> I have divided my database, creating a back end copy containing the tables
> and a front end copy with all the queries, forms, reports, etc..
> Now I have to send to 18 managers all around my country (Italy) both the
> databases and they must send me back every week the back end copy where they
> have registered all the sales in their areas. To avoid that they send me all
> the tables, I thought to divide once again the back end database to separate
> the sales table from the other tables of my database. So I've figured out
> the following situation:
> a.    the main database (sales.db), containing the engine of the
> application;
> b.    the first back end db (tables.db), with all the tables but the sales;
> c.    a second back end db (area_sales.db), with the sales of every area.

> But... never say never: I've found out that when I've divided the area_sales
> form the tables I've lost all the relations between the tables and I can't
> do anything because of the relational integrity rules. So I had to put the
> area sales back into the tables database and receive all the tables each and
> every week.

> Is there anybody that can help me?

> Thank you for your support, I hope that someday I will repay somehow.

> Riccardo Marcante

> {*filter*}s like us...



Tue, 03 Oct 2000 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Backend database link question.

2. Question, frontend to backend database same directory

3. Legal question - distributing access database files

4. Question About Distributing Access Database

5. Backend database crashing with Unrecognized Database Format

6. Form in backend database creates new user in frontend database

7. Copying table in Backend to another Backend

8. convert a backend Access97 to a backend Access2000

9. Access 97 frontend/backend to mySQL backend-Access frontend

10. Applicationm with 3 backend-databases


 
Powered by phpBB® Forum Software © phpBB Group