Hi,

I sometimes need to copy some data to create new inventory (I have a command button for that event). When I use it, I get a error message when I want to use the paste/append commands. The message states that the "paste/append function is not available at this time". After several months, we were able to identify when the problem occurs:

I have a database that grows fast and I need to transfer some of the information regularly to another database. I use two sets of linked tables: 1 for the current data and 1 for the "historical" data. Using the "openqry" command, I copy and transfer specific data from 4 different current tables to the according tables in the history database and I delete the current data when the copy is done. After the transfer is done, when I go back to the inventory and want to add new inventory I get the "error message" again. Actually this is the only time when it happens: after data transfers!

Does anyone know if I need to clear the clipboard or something ? Or do you know of a better way to transfer the data from one database to the other.

Thank you!

I too have this problem cropping up occasionally. After many frustrating attempts to resolve it we realised that it is not simply one problem. The things to check are (not in any particular order)

- network speed. If your network is trying to update remote(historic) tables using copy/paste it will not 'release' your master database until the append/paste is complete. Try putting DoEvents in your code. This will halt all processing until the OS/Network has caught up.
- database size. Check this regularly during a test run[use Filesystem.FileLen("database full path and name") or Filesystem.FileLen(CurrentDb.Name) for the master to display the size on a form]. You will be surprised how big your source and target databases become. We found that by compacting the master after a copy/paste, the errors did not appear. Unfortunately this can only be done by code if your master and remote databases are controlled through a 'switchboard' database and each is opened up in a separate Access window - not difficult, but not elegant either.
- your do not specifically say how you connect to the remote (historic)database but we found the problems (apart from database size) do not appear if you simply link the remote database tables to your master and use an Append query to transfer the data.

No techie solutions, I'm afraid, but I am confident that one of the above is causing your problem, If it is not please let us know.

Alan T