P
PedroDC
Greetings.
I created a PivotTable (PT) wich accesses an ExternalDataBase txt (EDB), and
enabled "Save data with Table Layout" option.
This EDB is obtained via exporting a table from Access.
The PT works fine. However, I cannot copy it to the local network, at work.
The copy process stalls and a file with the same name is created, however it
is corrupt.
There are, at least, three odd facts involved:
1. My IT colleagues can copy it to the network, taking a copy of the file
from my PC (using a flash drive), and performing the copy process on their
machines.
2. In January, I was using an Access Database (lets call it DB1) and
obtaining external databases in txt format, the same way I'm doing now. I had
a Pivot Table wich used the txt as ExternalDatabase, like now. However, I
never had any problem with the copying to the network phase!
3. Meanwhile, I copied DB1 (thus obtaining a DB2, wich I'm using now),
erased the data from the tables and importing new data (this was done every
month; again nothing new). The copying problem arises with the data I export
from this new table. This is the most weird thing, for me: if I erase the
data from this EDB, maintaing the headers, and copy into it data from, let's
say, December 2006 EDB, THEN I can copy the PT to the network.
What's happening???
I created a PivotTable (PT) wich accesses an ExternalDataBase txt (EDB), and
enabled "Save data with Table Layout" option.
This EDB is obtained via exporting a table from Access.
The PT works fine. However, I cannot copy it to the local network, at work.
The copy process stalls and a file with the same name is created, however it
is corrupt.
There are, at least, three odd facts involved:
1. My IT colleagues can copy it to the network, taking a copy of the file
from my PC (using a flash drive), and performing the copy process on their
machines.
2. In January, I was using an Access Database (lets call it DB1) and
obtaining external databases in txt format, the same way I'm doing now. I had
a Pivot Table wich used the txt as ExternalDatabase, like now. However, I
never had any problem with the copying to the network phase!
3. Meanwhile, I copied DB1 (thus obtaining a DB2, wich I'm using now),
erased the data from the tables and importing new data (this was done every
month; again nothing new). The copying problem arises with the data I export
from this new table. This is the most weird thing, for me: if I erase the
data from this EDB, maintaing the headers, and copy into it data from, let's
say, December 2006 EDB, THEN I can copy the PT to the network.
What's happening???