Just was playing around with that since I've never really had occassion to do it and always thought I knew how to if I needed to and I think I'm missing part of the step. If I have a DBC called ONE.DBC with a table called TABLE1 and I want to copy it to another DBC called TWO.DBC

I tried opening both DBCs, putting ONE!TABLE1 in the current work area and then
COPY TO TWO!TABLE1 but all that gets me is a table called "TWO!TABLE1" and there are no tables in TWO.DBC

What am I missing?

TIA

>>If we add some of our formerly-free tables to a DBC so that we can use transactions on them, what are the downsides? I am worried because I can't think of any right now other than the fact that the tables will not be accessible in older Fox apps (which is OK, we are all VFP 7.0 now). Usually when I can't think of anything that just means I am forgetting something awful... *smile*
>>
>>As far as I know, the tables should still open the same, have all the same indices available, etc. Can anyone point out any problem we may have with tables being part of a DBC instead of being free? If there is no downside, we will be ready to start using transactions more effectively!
>
>Hi Joek,
>
>One disadvantage is that if you need to copy the table (like to put it on a floppy disc and take it somewhere, you will need to create a new DBC, and copy your table and make it part of the new DBC so you won't lose long file names, etc. It's just an extra step in the process.