In MS Access 97 I'm using the CurrentDb.Name property (in a Visual Basic for Applications module) that gets the database path and filename. When it displays this path it shows as this (G is a network share):
G:\F0CWXX~T\G2VNK4~T\IO228C~A
when the path is this:
G:\Fundraising\GiftAttrition\Interface
I've tried it locally, and it shows the path correctly:
C:\Docume~1\username\desktop
It also appears to work correctly on a different network share.
So for network folders more than 8 characters in length it puts in those meaningless alphanumeric characters (although the first letters of the actual folders and meaningless ones match (F, G, I).
This database was created on a client PC, and when tested on another one, it did the same thing.
However, I created a test database on this other PC and it worked (showed the correct path folders), but when this test database was tested back on the first PC it did the same thing (strange characters).
I checked the Access setups on both PCs(to see what function libraries they use) and they're almost identical.
This issue isn't a major problem, as the weird path folders seem to "map" back to the actual ones, so when creating a file on the server using the weird names works. My only concern is that users who'll be using this database may get confused.
Has anyone seen this behaviour before?
G:\F0CWXX~T\G2VNK4~T\IO228C~A
when the path is this:
G:\Fundraising\GiftAttrition\Interface
I've tried it locally, and it shows the path correctly:
C:\Docume~1\username\desktop
It also appears to work correctly on a different network share.
So for network folders more than 8 characters in length it puts in those meaningless alphanumeric characters (although the first letters of the actual folders and meaningless ones match (F, G, I).
This database was created on a client PC, and when tested on another one, it did the same thing.
However, I created a test database on this other PC and it worked (showed the correct path folders), but when this test database was tested back on the first PC it did the same thing (strange characters).
I checked the Access setups on both PCs(to see what function libraries they use) and they're almost identical.
This issue isn't a major problem, as the weird path folders seem to "map" back to the actual ones, so when creating a file on the server using the weird names works. My only concern is that users who'll be using this database may get confused.
Has anyone seen this behaviour before?