Hi,
I am using FileSystemObject to count the number of files in a folder and up until a few months ago it always gave me the right answer in all the environments I use. Then suddenly the Windows 8.1 Pro development PC started to give an answer of 1 for all empty folders, whilst the Windows 10 PC gave the correct zero answer and so did the production environment on Amazon AWS where the server runs Windows Server 2012 R2.
Today I determined to find out the cause and examined the versions of scrrun.dll on the 3 systems. To my astonishment the Windows 8.1 and Server 2012 R2 versions were 5.8.9600.17415 whilst Windows 10 was running with version 5.812.10240.16384. The production version on the server is running an accde file and gives the correct answer, and the same accde gives the wrong answer on the development Win 8.1 PC.
Can anyone explain how this is possible? The actual line of code is:
intInvoiceCount = objFSO.GetFolder(DBPath & "\MMEMReprocessing").Files.Count
Many thanks in advance,
Sambodh
I am using FileSystemObject to count the number of files in a folder and up until a few months ago it always gave me the right answer in all the environments I use. Then suddenly the Windows 8.1 Pro development PC started to give an answer of 1 for all empty folders, whilst the Windows 10 PC gave the correct zero answer and so did the production environment on Amazon AWS where the server runs Windows Server 2012 R2.
Today I determined to find out the cause and examined the versions of scrrun.dll on the 3 systems. To my astonishment the Windows 8.1 and Server 2012 R2 versions were 5.8.9600.17415 whilst Windows 10 was running with version 5.812.10240.16384. The production version on the server is running an accde file and gives the correct answer, and the same accde gives the wrong answer on the development Win 8.1 PC.
Can anyone explain how this is possible? The actual line of code is:
intInvoiceCount = objFSO.GetFolder(DBPath & "\MMEMReprocessing").Files.Count
Many thanks in advance,
Sambodh