pcsoft.us.windevCopyright 2026, PC SOFT2 Nov 2014 18:26:00 Z2 Nov 2014 00:59:00 ZHello All Regular forum members will know that I have been complaining about the comparison program for some years now and while it is still incapable of handling large projects I have found a workaround. I start with the full project in one folder and in second folder I place about 250 files from the project I am comparing to. In practice this means that I create sets of files to compare starting with A to D and after comparing them, the next time I will do E to H and so on until I get to the end. I then do the same with the reports and then the queries. Limiting the second set of files means the comparison program does not run out of memory and crashes less often. The second folder with the subset of files must also have the project file in it for the project comparison option to work. I just ignore the messages about missing objects I have put a suggestion to tech support to provide an option to do this more easily by nominating a subset of files to compare. This would actually allow developers to perform comparisons by limiting the number of files to be compared to the capacity of their work stations. I can't compare two versions of a large project with 32gb of RAM but it certainly handles 250 files at a time, but if you have less RAM then maybe reduce the number of files you are comparing to. Interestingly, a bug in the comparison program that I first reported to tech support in V14 is still there in V19. When I run a project comparison, I always get a message that some objects are from a prior version . This should be impossible as Windev does the conversion from version to version so what has it been missing all these years and more to the point, if there are objects from a prior version, then mark them as such in the comparison program so I can do something about them. The comparison program issue is quite typical of PCSoft. A really clever concept, that could bring real time saving advantages to developers, is spoiled by half hearted execution and neglect over the years. Regards Al30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48755/read.awp2 Nov 2014 18:26:00 ZHello All One thing I should have mentioned. If you try this approach, use the 32 bit version in Windev19 as it is much more …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48755/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48755/read.awp[WD19] A method to compare large projectsguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48754/read.awp2 Nov 2014 15:22:00 ZHi Al and Piet, I hope PC Soft implements your suggestion. Our projects are small enough that we don't need a subset, but it …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48754/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48754/read.awp[WD19] A method to compare large projectsguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48752/read.awp2 Nov 2014 11:07:00 ZHi Al, Funny that you bring this up right after I tried for the first time comparing two Webdev pages (same WB version) and a…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48752/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/48749-wd19-method-compare-large-projects-48752/read.awp[WD19] A method to compare large projects