parse all text after the last \

Hi Klatuu,

Here is the C program I used (more or less) if it is any help to you.
I created three separate MDB files, one to test each method. In each MDB I
created the AutoExec macro to run the code and then quit out of Access.
Initially I had tested it in the reverse order and then had the thought you
had about order. The order did not seem to make any significant difference.
The Dir() method results did not surprise me because that does actual server
disk accesses and the other two methods do not. I expected your method to be
a little faster than using a FileSystemObject.

=================================================
// ProgramTimer.c

#include conio.h
#include process.h
#include stdio.h
#include time.h

int main(int argc, char* argv[])
{
clock_t clStart;
clock_t clEnd;
double dblSeconds;

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestMSR.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using FileSystemObject.GetFileName() (10,000,000
iterations): %1.3f", dblSeconds);

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestMid.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using Mid() and InStrRev() (10,000,000
iterations): %1.3f", dblSeconds);

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestDir.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using Dir() (200,000 iterations): %1.3f",
dblSeconds);

printf("\n\nPress any key to exit....\n");
_getch();

return 0;
}

================================================== ===

Sincerely,

Clifford Bass

"Klatuu" wrote:

I will admit to being very surprised and puzzled as to how loading the fso
object and doing the disk access is faster than intrinsic functions.

Whether it would make any difference, I don't know, but in some similar
timing test (not involving fso) I found the results would vary depending on
the order in which the tests were executed. I found where the results were
very close between two of the three, the first test run would show a better
time than the second.

That is not to dispute your results, but rather to offer information for
validation.

Now I am compelled to set up my own testing using 2003.

Please understand my intention is not to argue, but to collaborate.

Thanks

Did I understand you to say the fso does not require disk access?
How then does it get its directory and file information?

"Clifford Bass" wrote in message
...
Hi Klatuu,

Here is the C program I used (more or less) if it is any help to you.
I created three separate MDB files, one to test each method. In each MDB
I
created the AutoExec macro to run the code and then quit out of Access.
Initially I had tested it in the reverse order and then had the thought
you
had about order. The order did not seem to make any significant
difference.
The Dir() method results did not surprise me because that does actual
server
disk accesses and the other two methods do not. I expected your method to
be
a little faster than using a FileSystemObject.

=================================================
// ProgramTimer.c

#include conio.h
#include process.h
#include stdio.h
#include time.h

int main(int argc, char* argv[])
{
clock_t clStart;
clock_t clEnd;
double dblSeconds;

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestMSR.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using FileSystemObject.GetFileName() (10,000,000
iterations): %1.3f", dblSeconds);

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestMid.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using Mid() and InStrRev() (10,000,000
iterations): %1.3f", dblSeconds);

clStart = clock();
_spawnl(_P_WAIT, "C:\\Program Files\\Microsoft
Office\\Office12\\MSACCESS.EXE", "MSACCESS.EXE",
"D:\\ProgSrcs\\Access\\TestDir.mdb", NULL);
clEnd = clock();
dblSeconds = (double) (clEnd - clStart) / (double) CLOCKS_PER_SEC;
printf("\nSeconds elapsed using Dir() (200,000 iterations): %1.3f",
dblSeconds);

printf("\n\nPress any key to exit....\n");
_getch();

return 0;
}

================================================== ===

Sincerely,

Clifford Bass

"Klatuu" wrote:

I will admit to being very surprised and puzzled as to how loading the
fso
object and doing the disk access is faster than intrinsic functions.

Whether it would make any difference, I don't know, but in some similar
timing test (not involving fso) I found the results would vary depending
on
the order in which the tests were executed. I found where the results
were
very close between two of the three, the first test run would show a
better
time than the second.

That is not to dispute your results, but rather to offer information for
validation.

Now I am compelled to set up my own testing using 2003.

Please understand my intention is not to argue, but to collaborate.

Hi Klatuu,

My statement was based on a test I happened to do with a non-existent
path and file. Something like:

MsgBox fso.GetFileName("C:\abc.def\ghi.jkl")

It returned "ghi.jkl". So it was just parsing the name--no disk access.

Clifford

"Klatuu" wrote:

Thanks

Did I understand you to say the fso does not require disk access?
How then does it get its directory and file information?