On Wed, 01 Sep 2004 22:11:45 -0700, Tom van Stiphout
<no*************@cox.net> wrote:
On Wed, 01 Sep 2004 19:25:35 -0700, Larry Rekow <larry@netgeexdotcom>
wrote:
There are severe limitations to what you can do with macros. This is
one of them.
To paraphrase yourself: one day you'll discover VBA and its power, and
you'd wish...
-Tom.
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++
Won half the war. i destroy and make new tables each night after a
text report comes out of a UNIX box. Now I run a macro from access
that deletes the old table, copies an empty table (with the primary
key prefigured) to the table name I want. Then I do the transfer text
thing, importing the text report to a holding table. then run an
append query that appends the records to the new, empty table that
already has the primary key chosen on it. Not elegant, but workable.
but now my biggest problem: I can't seem to import this table from
Access to SQL and preserve the primary key. Googled all over, and
have had conflicting stories....some say you can't, others say you
can. Certainly if I could do it all using SQL DTS, I would, but I
can't figure out how yet.
Certainly if I did it manually, i guess I could do the Access upsize
wizard....that's supposed to keep the primary key..but it's not
automated.
so now i guess i'll have to find out how to use either VBA or VB.net
to see if i can make some sense of it all.
sheesh.
Larry
- - - - - - - - - - - - - - - - - -
"Forget it, Jake. It's Chinatown."