How to save (and/or obtain) import Textfile file steps?

[EagleOne]

2003/2007


Have need to import massive 2MM plus record files from MF.

The MF files have headers of more than one line.

I would like a ACCESS macro to delete the first three "rows".

Then, either before or after the import, to rename & DataType the fields (columns)

That said, I do not believe that I can record a macro in Access (unlike Excel).

Yes, I can save the import as a "Saved Import" but what do I do to re-run that in Access 2003?

In short, I would like to save all import text-file steps (including renaming and DataTyping) in a
re-runnable macro. Preferrably, in the VBA module as I am more familiar with VBA as opposed to the
Access macro builder. (That said, I believe that I could convert it and have it both ways?)

Would someone supply a textfile import macro that I could edit? Or let me know how to "get to" the
saved import steps on 2007 for use in 2003.

Please include steps for renaming and DataTyping.

Also, how do I call the macro? Button?

TIA EagleOne

 

[a a r o n _ k e m p f]

anyone using more than 10,000 records of _ANYTHING_ needs to move to
SQL Server

prior to 2001, I worked with tons of million-row Access databases.
It makes me sick to think about how much man-power my reports wasted..
just because Access doesn't scale well.

Just move to SQL Server and use something like DTS or SSIS in order to
automate the process.
It's like the difference between

a) growing your own chicken- to get one egg per day
b) going to the store to get a dozen once per week.

Which is _REALLY_ more expensive?

-Aaron

 

[EagleOne]

With all due respect, I requested simple information. I get a sermon. And I bet you could have
,just as easy, given a helpful response.

How could you possibly give that answer without knowing the application?

With arrogant responses like yours you live with constant egg-in-your-face.

It is no wonder Access lags behind Excel in acceptance. With Access NG's like this MS is wasting
its time.

 

[a a r o n _ k e m p f]

if you want to find a database, go use SQL Server

this Access stuff is just a joke-- it doesn't scale, it's not
portable-- and I don't want SharePoint shoved down my throat.

 

[a a r o n _ k e m p f]

anyone (trying) to use 2m records in Access should be:

a) fired
b) spit upon

there are a half dozen kids on craigslist that will do the job right
for you.

 

[Bob Larson]

Smeg Off

Don't be such a whiney snot. If you want to get people to see your points
you need to not sound like a two year old who is whining because the dog
took his ball. Go step on a land mine - it would do more good for the world
than continuing to post.

anyone (trying) to use 2m records in Access should be:

a) fired
b) spit upon

there are a half dozen kids on craigslist that will do the job right
for you.

 

[Larry Linson]

anyone (trying) to use 2m records in Access should be:
a) fired
b) spit upon
there are a half dozen kids on craigslist that will do the
job right for you.

Mr. Kempf, insulting the poster is not helpful.
None of your other posts to this poster have been helpful, either.

When you can do nothing but vent your venom, please exercise some restraint
and resist the urge to do so in these newsgroups -- that would be helpful.

Larry Linson
Microsoft Office Access MVP

 

[a a r o n _ k e m p f]

Larry;

You DAO is too buggy for real world usage.

Your JET database is not stable enough for more than a single record
and a single user.

Don't shoot the messenger.

-Aaron

 

[a a r o n _ k e m p f]

Bob;

I am so sorry that you don't have the balls to learn a real database
engine.

Don't blame me. Maybe you should take databases seriously.

JET is dead and it has been for a decade. No truckloads of SharePoint
will change the equation.
It's just better to use SQL directly than SharePoint (because of all
the extra layers)

-Aaron

 

[Bob Larson]

I got more balls than you have bunghole. I know SQL Server too, believe it
or not. My current project is working with SQL Server and optimizing it.
So FO MOFO as you don't know SH#@ AND you don't know me. Do the world a
favor and go stick your tongue in a 240V dryer socket. You are the scum of
the earth - not intent on helping anyone - just intent on spouting off and
making yourself feel like a big man (of course you are just a baby).

So go take 1000 valium.


Bob;

I am so sorry that you don't have the balls to learn a real database
engine.

Don't blame me. Maybe you should take databases seriously.

JET is dead and it has been for a decade. No truckloads of SharePoint
will change the equation.
It's just better to use SQL directly than SharePoint (because of all
the extra layers)

-Aaron

 

[a a r o n _ k e m p f]

bullshit.
you don't know jack shit about SQL Server.

if you knew SQL, you would not be using Jet for any reason.

I mean seriously-- Are you usign SQL Passthrough? How many steps does
it take to bind a form to a sproc?
Because ADP can do it in 1 step.

Case closed. You're not as knowledgeable as you claim, huh?
Are you certified in SQL Server? I'm MCITP: DBA, thanks.

So sorry that you don't have the cojones to stand up to dipshits that
reccomend 'not to use Int, BigInt for Primary Keys'.

Seriously-- the MVPs around here are ****ing bullies and idiots and I
won't stand for their misinformation, not for another minute.

 

[Larry Kahm]

EagleOne,

Your best bet would be to use a mainframe SORT job to drop the first three
records >before< you do the download. That way you don't have to concern
yourself with how - or even if - Access can do it.

//S1 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD DSN=... your input file
//SORTOUT DD DSN= ... your output file
//SYSIN DD *
OPTION COPY
OUTFILE STARTREC=E
/*

That should do it.

Larry