By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,107 Members | 1,323 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,107 IT Pros & Developers. It's quick & easy.

.NET and TableDefs.Append

P: n/a
I am trying to diagnose a rather insidious problem. Yesterday, I tried to
install the .NET Framework 1.1. That installation failed. No big deal -- I
can live without it.

Now, however, none of my MS Access applications work. I've researched the
problem and found that whenever the DAO TableDefs.Append method is executed
in code, I get Run-time error '3001': Invalid Argument. I am confident that
the VBA syntax is correct, since the same code worked flawlessly up until
yesterday, and it continues to work on my test computer.

On the surface, it would appear that the failed .NET installation has
somehow corrupted DAO. Does that make any sense? More to the point, how do I
fix it? I am using Access 2000 and Windows 2000.
-Todd Matson
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
As often happens, I've learned a little more about this problem since my
post. It seems I was hasty to blame .NET for the trouble; I now believe the
problem was caused by one of the security updates I installed yesterday. To
place this conversation under an appropriate subject heading, I am going to
terminate this thread and start a new one.

-Todd Matson
"Todd Matson" <q@w.e> wrote in message
news:XZ*************@news1.central.cox.net...
I am trying to diagnose a rather insidious problem. Yesterday, I tried to
install the .NET Framework 1.1. That installation failed. No big deal -- I
can live without it.

Now, however, none of my MS Access applications work. I've researched the
problem and found that whenever the DAO TableDefs.Append method is executed in code, I get Run-time error '3001': Invalid Argument. I am confident that the VBA syntax is correct, since the same code worked flawlessly up until
yesterday, and it continues to work on my test computer.

On the surface, it would appear that the failed .NET installation has
somehow corrupted DAO. Does that make any sense? More to the point, how do I fix it? I am using Access 2000 and Windows 2000.
-Todd Matson

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.