VictoriaLJones
Technical User
Hi,
I have been asked to help with a db conversion from NT & v97 to XP & v2000/2. Prior to converting the db, the team used to import a text file with a .F16 (The exact ending will be determined by the date, so I cannot hard code .F16 as an option) file ending, which is a text file.
However after converting over to XP and 2000/2, it no longer recognises .F16 as a valid file type. The code that has been written is:
DoCmd.TransferText acImportFixed, "DPR Import Specification", "DPR", FileName, False, "" 'Import File base on FileName
I am unfamiliar with this command, and am not sure how to get round it - if we can.
At the moment the option is for me to write a macro (either in Excel or I could call Excel from Access) to convert the file from .F16 to .txt, as Excel does open/recognise the file. However is there a function in Access that could do this, without using Excel, or is there a way to disable this function in access 2000/2.
Any ideas would be great!!!
Thanks in advance!
Victoria
I have been asked to help with a db conversion from NT & v97 to XP & v2000/2. Prior to converting the db, the team used to import a text file with a .F16 (The exact ending will be determined by the date, so I cannot hard code .F16 as an option) file ending, which is a text file.
However after converting over to XP and 2000/2, it no longer recognises .F16 as a valid file type. The code that has been written is:
DoCmd.TransferText acImportFixed, "DPR Import Specification", "DPR", FileName, False, "" 'Import File base on FileName
I am unfamiliar with this command, and am not sure how to get round it - if we can.
At the moment the option is for me to write a macro (either in Excel or I could call Excel from Access) to convert the file from .F16 to .txt, as Excel does open/recognise the file. However is there a function in Access that could do this, without using Excel, or is there a way to disable this function in access 2000/2.
Any ideas would be great!!!
Thanks in advance!
Victoria