dots in filenames throws error when trying to link tables

[stuey]

I've been using MS access to lift some text files for a number of years

I have now got an issue where by the new machinary is very clever and has alittle server to collect the data. Machine1_127.0.0.1, Machine2_127.0.0.1

Previously I picked them up via ftp and downloaded the data into a text file called Machine1.txt

Now I can run a server where by the Machine1_.txt is created locally on the processing machine

however the software included ( which I can't change) just creates text files like so Machine1_127.0.0.1 and now the link doesn't work when I create the link access throw this:

"Microsoft Jet Database engine could not find the object c:\Path to file\Machine1_127.0.0.1.txt. Make sure the object exists and name and Path are correct"

If I manually copy the file and rename it to machine1.txt all is good

Any offers/thoughts or suggestions, the path is quite deep at present and that could be changed.

I can't import the files either? unless I rename them and at the moment I am doing this through the interface

 

[GaryPanic]

OK- cannot resolve - but
MS office and your server expect files extentions to be .doc . xls

so i think its this that is causing a problem - when you rename manual the server is looking at the file type correct - however when automated its not -

no0m idea howm to resolve - but highlighting the problem might help someone point you in the right direction

 

[Deleted member 30250]

I have a function (attached) that imports a pile of dbase tables from an Approach application. The problem there is that I have to reduce the filename to 8 characters otherwise Access just refuses to see them. So the function attached finds any *.dbf filenames, messes about with the names then imports all of them. This is obviously not the same problem as yours, but I wonder if you could use the filesystem idea to find files called Machine1_*.* and manipulate the names in some similar way to produce copies?