VB Modules copied to different project folders get corrupted 
Author Message
 VB Modules copied to different project folders get corrupted

I have a series of programs done in VB 5 which use most of the same code
modules (.bas) files and Form (.frm) modules.  For each project, I copied
all the files from one project folder to another.  There are small but
crucial differences in the modules from one project to another, though the
modules' names remain unchanged.

In saving, archiving, and transferring files from one machine to another,
I've noticed that changes are not always saved; files seem to revert back to
earlier versions.

I've been very careful of my habits for over half a year regarding this
practice, in case this is due to my oversight.  I now suspect that VB does
something to reconcile modules of the same name even if they are in
different folders.

Am I nuts or is something going on here?

Thanks,

John Cummins



Sun, 25 Nov 2001 03:00:00 GMT  
 VB Modules copied to different project folders get corrupted
John:

Even though you may have a separate copy of a .bas file in each project folder,
this does not automatically ensure that each project in fact uses the copy of
the .bas file that is in its particular folder.  On a number of occasions I have
found that my  project was using a copy of a .bas, .frm or .cls file that was in
a different folder than the one I had intended.  One way to be sure, is to do a
"Save As" for each file in each project to ensure that files in the project are
indeed the ones you intend to use.  You can also examine the project's .vbp file
with a text editor to check the paths used for each file in the project.

John........

Quote:

> I have a series of programs done in VB 5 which use most of the same code
> modules (.bas) files and Form (.frm) modules.  For each project, I copied
> all the files from one project folder to another.  There are small but
> crucial differences in the modules from one project to another, though the
> modules' names remain unchanged.

> In saving, archiving, and transferring files from one machine to another,
> I've noticed that changes are not always saved; files seem to revert back to
> earlier versions.

> I've been very careful of my habits for over half a year regarding this
> practice, in case this is due to my oversight.  I now suspect that VB does
> something to reconcile modules of the same name even if they are in
> different folders.

> Am I nuts or is something going on here?

> Thanks,

> John Cummins




Sun, 25 Nov 2001 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. VB6 project getting corrupted.

2. Access to methods in a standard module in a different project

3. Copy a file in a folder and past the copy in another folder

4. Creating a file folder when project gets published

5. VB4.0a / NT 4.0 Server + SP2 and corrupted VB projects

6. Q(VB5) : Different between module & class module

7. VB setup gets registry corrupt error on client machine

8. VB setup gets registry corrupt error on client machine

9. VB setup gets registry corrupt error on client machine

10. Copying files from different locations to different locations

11. copy module to another module

12. Can It be possible to access the module of one project into the another project

 

 
Powered by phpBB® Forum Software