Extra "." (dot) in filename before the dot3 file extension....

  • Thread starter Thread starter Raymond
  • Start date Start date
R

Raymond

Hello,

I'm concerned about potential problems as a result of working with files
that have an additional "dot" in the file name; additional to the dot3 file
extension.

I will be working primarily with file types from Adobe Acrobat and MS Office
Suite within the Windows XP operating system, and with email and FTP
internet protocols; however, external clients and future needs may indicate
other applications for these files...

Can anyone inform me of potetial issues with the use of "." (dot) in file
naming?

Thanks in advance,

Raymond
 
Are you talking about files named like this: MyFile..dot3

And what do you want to do with those files in ACCESS?
 
Hi Raymond,

Since you've asked in an Access newsgroup I presume you're only asking
about problems Access may have working with files that have more than
one dot in their names (or to put it another way, where there may be
one or more dots in the name as well as a dot between the name and the
extension.

Unfortunately there are some bits of code in and around Access (as of
Access 2003, I haven't checked 2007) that fail if there are multiple
dots. Presumably they are left over from 16-bit days and assume that
the first dot in a filename marks the beginning of a 3-character
exension. (Hands up anyone who hasn't written code that does that...)

I don't have chapter and verse. A recent thread in this group showed
that it's an issue with TransferText (but not, perhaps surprisingly,
with the even older VB file I/O functions). The subject was
File names causing a problem
starting on 7 August 2007.

Most likely the problem is confined to ancillary routines such as
TransferText. It should be possible to work round it when importing or
linking by using the short name corresponding to the multi-dotted
filename (you can get it by using the FileSystemObjectObject).
 
Unfortunately there are some bits of code in and around Access (as of
Access 2003, I haven't checked 2007) that fail if there are multiple
dots. Presumably they are left over from 16-bit days and assume that
the first dot in a filename marks the beginning of a 3-character
exension. (Hands up anyone who hasn't written code that does that...)
Click to expand...

Y (person staning with both hands up)

I've never done this.. < g >.

I always start at the end of the string and find the 'last" dot in order to
determine the beginning of an extension. But then, I'm a relatively newcomer
to programming.....! < chuckle >
 
And I always put dots in my dev folders to make sure never to do that (even
back in the 16 bits world)
I have had a few gotcha's with spaces though ... <g>

Pieter
 
Back
Top