Visual Studio .Net causing Visual Basic 6 problem?
Perhaps I didn't get the order of problems correct in my previous message.
I could not even run VB until I re-registered DAO350.DLL. After I was able
to run VB at some point I tried to add a new command to the Data Environment
and to set its properties in the properties window. That is when VB started
crashing.
After posting the problem to the newsgroup, I worked around the problem by
using code instead of working in the data environment and finished my VB
project.
Later I revisited the problem to see if it was still there. It was. Each
time I created a new command and tried to set its command type using the
properties window, VB would crash. I then recalled that there was another
way to set the properties of a newly created command: Right-click on the
command and set the database object and object name there. This didn't
cause VB to crash.
So I left things there.
Today after seeing your message, I looked at the project again and tried to
set the command type of a newly created command in the properties window.
And this time there everything worked fine.
I can not point to anything that changed to make things work correctly. For
two days the problem was there, and now it is gone. I did use Visual Studio
.Net earlier in the day; although, I can not imagine how that would have
helped things.
I still have the Visual Studio Command Prompt on my most recently used
programs on the start menu--even though I have never used it.
Quote:
> When you re-registered DAO350.DLL did the DataEnvironment problem also go
> away? Also, did the DataEnvironment scnario ever work after you installed
> VS.NET? Did you install/uninstall anything after installing VS.NET?
> Thanks,
> Mike Bond
> Microsoft Visual Basic Development
> --
> This posting is provided "as-is" with no warranties, and confers no
rights.
> (C) 2002 Microsoft Corporation. All Rights Reserved.
> > I am using VB 6 with service pack 5 on Windows XP professional. I also
> have
> > Visual Studio .Net installed on this computer. VB was installed first.
> > After installing VS . Net, at first I noticed no problems, then strange
> > things began to happen. They are:
> > 1. In Visual Basic, in the Data Environment of a project when I add a
> > command object for a connection and try to set any of the command
> > properties, I receive the message:
> > "Visual Basic has encountered a problem and needs to close. We are
sorry
> > for the inconvenience". At this point, VB 6 closes.
> > 2. When I started VB the other day, I received a message to the effect
> that
> > the file dao350.dll couldn't be found. Then VB closed. I checked and
it
> > was indeed on the computer in the folder C:\Program Files\Common
> > Files\Microsoft Shared\DAO. I then simply reregistered the DLL, and VB
> > opened fine.
> > 3. Without ever having used the program, Visual Studio .Net Command
prompt
> > now appears on my recently used programs when I click on Start.
> > Anyone else seen anything like this? Visual Studio .Net seems to be
> working
> > fine, but VB appears to be getting a bit flaky. Problem 1. above is,
in
> > fact, serious for me. Of course, I could reinstall VB and service pack
5,
> > but will wait on that for awhile.
