>No, I don't think you are being "thick" on this one. Your point and approach is well taken. There are many times that "we" as developers tackle things almost with a "one track mind" and later on we find a "six million dollar man" solution. If I had to redo it again, I would certainly try something along the lines of your approach, but for now, the client will not be pleased with an additional re-engineering bill.
>
>Regardless of approach, what is really wrong here? Is it a macro substitution deficiency or an OS problem. According to Ken Weber on this thread, the sample code that I provided works well under Win95. I however, am using NT 4.0 and it fails miserably.
>
>I happen to feel that it is a macro substitution deficiency or anomally because the same file name can be used in a USE statement with no problem.
>
>ie.
>m.lcPath = "c:\December 1998\test.dbf" && Note, no quotes
>USE ( m.lcPath )
>
>As you can see my finding supports your approach.

Hi Juan,

I do try to take as many externals (like the OS) out of the equation as possible. I don't know if this will work on NT or not, but it does on Win 95/98. Further, it may not meet your needs, depending on how specific your example was. However, might try:

SELECT *;
  FROM (m.lcpath)
  INTO ARRAY aFees

where m.lcpath is the name of your table.

hth,