Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 1 / December 2005

Tip: Looking for answers? Try searching our database.

VBA Editor Crash!  Dot Net Framework Guilty!!!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
b - 01 Dec 2005 13:26 GMT
I'm using Access 2003 SP2 on XP.

For some reason, after I install MS .Net Framework (1 or 2), my VBA
editor (through Access) crashes.  If I uninstall the .Net Framework,
everything works fine.

Has anyone else had this problem?

How did you solve it?
Tom van Stiphout - 01 Dec 2005 13:44 GMT
Eh, by uninstalling the framework?  :-)

No really, the two have little to do with each other. You must have
some other nasty incompatibility on your system. In our office we're
running them side by side on several computers, and no problems.

-Tom.

>I'm using Access 2003 SP2 on XP.
>
[quoted text clipped - 5 lines]
>
>How did you solve it?
b - 01 Dec 2005 13:54 GMT
Exaxctly!

Problem is that I need to have both installed on the same system.

I wonder what I could look at to start troubleshooting this issue?
Wayne Morgan - 01 Dec 2005 14:53 GMT
Make sure all your Windows and Office patches are up to date. There may be a
dll that was updated by the .Net install that is conflicting with another
old dll, but this is just a "hope for the best" attempt to fix the problem.
Also, make sure you have installed the most current drivers, especially the
video driver, for you system.

If that doesn't work and you have a spare hard drive, even an old, small
one, try using it to do a test, clean install of Windows, Office, all
patches, and any other programs you have to have and see what happens.
Install only the first 3 items first then the other programs one at a time
so that you can isolate where the conflict is if one should occur.

Signature

Wayne Morgan
MS Access MVP

> Exaxctly!
>
> Problem is that I need to have both installed on the same system.
>
> I wonder what I could look at to start troubleshooting this issue?
b - 01 Dec 2005 17:34 GMT
Thank you both!

Wayne:  You hit it on the head!

Apparently, my dual monitor video card uses some .NET code for some of
it's options/features.  When I updated the driver, it warned that I did
not have the .NET framework installed and some features would not be
available.  hint hint...

So, I updated the video card driver and reinstalled the .NET Framework
1.1 and all is well!

On a side note, it did not like the .NET 2.0.

Thanks again!

Bob
David W. Fenton - 01 Dec 2005 20:27 GMT
> Apparently, my dual monitor video card uses some .NET code for
> some of it's options/features.  When I updated the driver, it
[quoted text clipped - 5 lines]
>
> On a side note, it did not like the .NET 2.0.

I just can't believe how badly Microsoft has botched .NET.

Of course, this was from the company that brought us DLL hell, so I
guess it shouldn't be a surprise, but it makes a mockery of the
whole *point* of the .NET framework if programs built to run on it
need specific versions of it.

Once again, I find myself breathing a sigh of relief for not having
drunk the MS Kool Aid on one of their "new platform" initiatives.

Signature

David W. Fenton                        http://www.bway.net/~dfenton
dfenton at bway dot net                http://www.bway.net/~dfassoc

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.