I have a Listview with subitem which i add populate data in listview which is lengthy, i want to shorten the code, i tried For loop but it give me error at run time. With Do loop it working.
I see what you mean. The modules are there but not in the solution explorer.
That could happen when the module is in an assembly that's registered in the GAC, taking precedence over another copy. That doesn't explain why the IDE picks the code up as "changed".
Open the solution file (.sln, in the root of the project-directory) in notepad, and verify that it ain't the same files. Now and then I make a "link" instead of a copy when adding a file from another project - changing the file in one project would then cause the other IDE to "see" the changes and ask whether it should reload.
I think it happens if you double click on a file that goes to VisStudio. It adds the file to the solution
Not on my machine; had a solution open, double-clicked on a non-related sourcefile from another project. It opened, could be edited, but was not added to the solution, nor is the filename mentioned in the solution-file.
I have seen this before. I have a solution open and I want to view a vb module with notepad but I double click on the modules and it defaults to Vis Studio. That module is not 'in' the solution that I have opened. I have since changed the default program on .vb, etc. to Notepad but this is a 'new' machine and for the first few weeks it was not set.
Well I have no other idea how a module not related to a program can get into it, not be in the solution explorer.
I know VB6 is no longer supported from Microsoft, but he is our Old Client and i have to do a lot of things as per your recommendation. I have to get data faster (huge and from multiple table) only on 2 forms and that's it. so please if you can help.
I did; see the previous post, there's a link to a CodeProject-article that explains how to run a stored-procedure using VB6.
Yusuf Mohammad wrote:
I know VB6 is no longer supported from Microsoft, but he is our Old Client
I wish your old client lots of success; if he's not migrating yet, he's setting himself up for a huge problem. Like I said, VB6 isn't for sale anymore, and newer Windows-version will not be tested with VB6 applications. There's no guarantee that any VB6-app will still work tomorrow, any update could kill it.