Okay, I don't have an example to hand. I suspect one of the MVPs did, but I
can't recall whether it was Duane or Albert or one of the others.
If we assume you have a form based on a crosstab (so you've sorted out the
issues associated with the changing field names that the crosstab may
generate), you have a Continuous form. When you click on a text box and drag
it somewhere else, its mouse events fire (so you know the source box.) Its
Mouse Up event will give you the offesets (X and Y) in twips (1440 twips = 1
inch), so based on that you can calculate what control the mouse was over
when the user completed the drag. (It's actually a bit more complex than
that, as the user may not have clicked on the current record row.)
Now you want to respond to that by moving the value from the source into the
target. Execute 2 update queries: one to update the target with he source
value, and the other to update the source to Null. Then requery the form so
it shows the update. (You'll need to save enough info to identify the
current record first, requery, and then FindFirst. This may cause the
continuous form to scroll in an undesirable manner.)
As I say, that's off the top of my head, but hopefully an idea you can
develop.