I know this has been discussed before and yes, using multiple procedure per module is a fix.
but..
When using Version control, especially Upper Parks - it is 1 procedure per module.
Here is the case.
I usually develop locally and everything works on my machine, but when we try and compile on another workstation they get this error. Is machine configuration a factor in this
are there additional IDE setting that may be wrong on the developer machine>
As far as I know, machine resources does not matter. The problem are the 32 bits limits in source internal references tables or something like that; if you have “too much” in a single source, this pops no matter if you are in a supercomputer.
Regarding the “everything works on my machine but not in theirs”, are the Clarion templates exactly the same? One template generating an extra line may be pushing the code over the edge limit.
Same with the solutions files, are the SLN and CWPROJ files exactly the same as well? Once more, a few bytes added in a different resource can push the limit if you are already at the border.
Also yes, IDE settings may cause this, for example build mode; are both in release mode, both in debug mode or are you using different compilation modes?
I wonder if the Windows environment path is a factor and the RED file, plus is the other workstation using the folder location as a mapped drive [A-Z]: or UNC \\ComputerName\Folder ?
I dont think Clarion likes UNC so doing a manual mapped drive could help.
Plus is any antivirus software monitoring the folders which could be causing a problem, like repeated file scans?
No, I am going to have to break these apps into further DLLs (honestly should have been done before this - but client hates me spending time on “refactoring” code. When it was just me (13+yrs) i made changes as I saw fit. But now, I have been told I cannot make changes without authorization (my productivity is greatly reduced due to this). So now that that they want Multi-Developers/Source control it need their permission to do this - so waiting..
Kind of a malicious compliance thing going on - I will update when status changes.
One thing I’ve found using source control with Rick’s tool.
Even if you as a developer have release mode for the app generation, that doesn’t stop other developers working on the repo being in debug mode. For one specific client, this has caused similar issues to what you mentioned.
Might not be the case, but thought it was worth mentioning.
In case it helps, note that you can disable the debug mode (changing it to release) just for the particular clw where you are getting the too many files error. (Editing the properties from the solution tree).