' GetShortName("C:\Users\Daniel\Desktop\XBase - dBase sample data.dbf")
' sFile : Path and filename including extension to convert format ' Req'd Refs: None required, Req GetShortPathName Declaration ' Copyright : The following is release as Attribution-ShareAlike 4.0 International ' Purpose : Convert a LongFileName to a ShortFileName (think DOS!) ' Modified Daniel Pineault, CARDA Consultants Inc. Public Declare Function GetShortPathName Lib "kernel32" _ I wondered if by simply converting formats Access might be happy once again and perform the Import/Link. We’re living back in the days of DOS.įunny enough, it’s actually that very thought, that gave me the solution to this issue!īack in the days of DOS, you couldn’t have these super long file names like we do today and the format is now known a ShortFileName and there’s a simple API that enables us to convert a LongFileName into the old ShortFileName format. So, it would seem that Access can’t handle dbf files with filenames that are more than 8 characters long. Have you ever needed to Import or Link a DBase DBF file in an Access? If your DBF filename is longer than 8 characters you’ll be in for a nice treat!Īnd once you click OK, you’ll get a nice error!!! This change is rolling out to O365 customers, and should be available to all (if not already) very shortly.” (which corresponds to Office365 Build 1807). Before going any further, the workaround elaborated in the following article may no longer be necessary as I am happy to announce that the Access Dev Team just informed me that they have “added support for longer dBase file names, and currently support up to 64 chars.
0 kommentar(er)
