Well, the locking file keeps track of who is in the file, and each file
should uniquely have its own LDB. They risk bizarre locking problems that
would be hard to diagnose by keeping them in the same directory with the
same name (putting the MDW in a subdirectory might by the easiest thing to
do, changing the name of the MDW would be another).
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
Windows International Division
This posting is provided "AS IS" with
no warranties, and confers no rights.
"TR" <t_NoSpam_redick@Mind_NoSpam_spring.com> wrote in message
news:40E198F0.CAA9C335@Mind_NoSpam_spring.com...
Thats what I figured.
Its not what I would normally do. But I've just been assigned to make
some changes to a legacy Access 95 application (yes, really). The
application is working as far as I know (I really no very little about
the app, its huge, I'm just adding some fields to some pre-existing
reports). Are there any particular reasons I can provide for suggesting
they change their naming convention?
Thanks,
Tom
"Michael (michka) Kaplan [MS]" wrote:
Tons. You should not do this.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
Windows International Division
This posting is provided "AS IS" with
no warranties, and confers no rights.
"TR" <t_NoSpam_redick@Mind_NoSpam_spring.com> wrote in message
news:40E16C57.7463E3C3@Mind_NoSpam_spring.com... Hi,
Just wondering if there are any issues involved with using the same
names for access files of different types, ex. filename.MDW and
filename.MDB. When these are both in use and reside in the same
directory, Access creates one LDB file, filename.LDB. Are there any
potential problems with this scenario?
