A
azu_daioh
Hello,
I split the database into backend and frontend. When I run the reports
in the FrontEnd - it took a long time to process. The backend is
stored in a centralized server (ie. North California) and I'm located
in the Southern California. I don't know if the physical location has
something to do with the speed but accessing the BE from the FE for me
is way too slow. I do want to keep the database split tho' -- it causes
less error.
Anyway, what I'm trying to do is to create another database solely for
reporting purposes. It will not contain any table except for the one I
will be importing from the BE file. I used the macro TransferDatabase
which worked fine at first attempt but when I tested it again, it
created a new importedData table (it added a number in the end)
Is there a way I can import a table from another database and maintain
the same table name? I don't want to end up with 12 tables every year
(I run the report once a month).
Thank you,
Sharon
I split the database into backend and frontend. When I run the reports
in the FrontEnd - it took a long time to process. The backend is
stored in a centralized server (ie. North California) and I'm located
in the Southern California. I don't know if the physical location has
something to do with the speed but accessing the BE from the FE for me
is way too slow. I do want to keep the database split tho' -- it causes
less error.
Anyway, what I'm trying to do is to create another database solely for
reporting purposes. It will not contain any table except for the one I
will be importing from the BE file. I used the macro TransferDatabase
which worked fine at first attempt but when I tested it again, it
created a new importedData table (it added a number in the end)
Is there a way I can import a table from another database and maintain
the same table name? I don't want to end up with 12 tables every year
(I run the report once a month).
Thank you,
Sharon