TransferSpreadsheet command crashes application--SP2 needed?

[rlntemp-gng]

re:Access 2003
TransferSpreadsheet has worked in my app for weeks now.
Now, the day I was to put in production (today) it crashes the app,
and users are livid...but not more than me though..embarrassed is more
like it

As an outside test, I built a "DummyApp.mdb" with a form, and a
command button that only performs a transferspreadsheet on the same
Excel file as my production app is using. The DummyApp works fine.
what has caused this.
Since the dummy app worked, I went back and have painstakingly walked
the code tirelessly trying to find if there is anything else causing
this.
The excel file layout has not changed at all.

Not sure what the problem is or how to even fix it, short of just
linking to the sheet directly and forgetting TransferSpreadsheet
command all together. Why does this command work in one .mdb but not
another? There is no fancy code around my transferspreadsheet code in
my problem app.

I came across a "post service pack 2 hotfix for Access" and printed
it. It referenced there was a problem with TransferSpreadsheet
crashing an application.
So, I thought well, I must need this SP. I went searching on the MS
website. Clicked a link for downloading SP2 and was taken to this
page:
http://office.microsoft.com/en-us/do...CL100570421033

There HAS to be a faster way to get to the SP's and subsequent
hotfixes for Access so I can install them?

I am very nervous about decompiling/recompiling. Never done it yet.
Don't want to destroy the application doing this. Despite my
hesitations, is this a viable solution to this problem?

Many thanks.

[lyle]

On Aug 1, 10:00 am, [e-mail] wrote:

re:Access 2003
TransferSpreadsheet has worked in my app for weeks now.
Now, the day I was to put in production (today) it crashes the app,
and users are livid...but not more than me though..embarrassed is more
like it

The first rule of Access Applications is:
"When you deliver, it won't work!"

If you haven't felt the heat and sweat creeping up over your shirt
collar, and wanted the floor to open and swallow you up, you're not
really a Developer, yet. If you haven't driven away from the client's
building saying, "Oh my God, what an a__hole I am", you're either the
Messiah or a neophyte.

The thing is, I've never had a client yet who reproached me, or didn't
give me a second, third or even fourth chance.

I am very nervous about decompiling/recompiling. Never done it yet.
Don't want to destroy the application doing this. Despite my
hesitations, is this a viable solution to this problem?

Who knows? I have never found decompile helpful, but others think it's
the greatest thing since Lauren Bacall. I save everything as text and
reload it.
But what could decompile hurt? You have only one copy of the
Application? Make another. Make several others. Then do the decompile
on one. What could it hurt?

When I develop I create a subfolder called Safety. At the end of each
day, or hour, or change, depending on the nature of the application I
make a copy of the applcation as eg ESO200708011011.mdb, and I backup
all the objects as Text. Every night I back these new safeties up to
an external hard drive and to an off-site computer. Every month or so
I put them on a CD and put the CD in a safety-deposit box. For some
applications I have literally hundreds of dated backups. (Of course,
my apps are small; I like it that way).

You might get more help on the actual problem if you provided more
information than "crashes the app"; I can think of several ways an app
might crash. BTW, does it crash on the same computer where you tested
it, or on another computer?

[rlntemp-gng]

>>BTW, does it crash on the same computer where you tested it, or on another computer?

It crashed on one computer only. There were other issues with that
machine and a re-image fixed it.

I have taken your "safety" folder to heart, and created one for
myself. Thank you for that tip.

Going forward, I am putting a task item in Outlook each time I post a
question, so that I do not forget to reply. It's September 14th, this
post was the originally the first of August, which makes me appear
ungrateful for your reply. Rest assured, nothing could be further
from the truth. "Plain and simple screw up" is my excuse on this
one. :-(
I was late.....(oh so very late) on this reply, and I sincerely
apologize. :-)