Required 8.3 filenaming convention?

[Westy]

In the Servoy Developer Volume 1 - Users Guide on page 497 it states:

IMPORTANT: If you are creating an iAnywhere database as a service on Windows 2000, make sure that you use the 8.3 naming convention...

Is this true, or should it say Windows NT? Long file and folder names seem to work fine on the Windows 2000 Workstation PC that I am using for testing purposes. If anyone can clarify this I would greatly appreciate it.

[mnorman]

In the Servoy Developer Volume 1 - Users Guide on page 497 it states:

IMPORTANT: If you are creating an iAnywhere database as a service on Windows 2000, make sure that you use the 8.3 naming convention...

Is this true, or should it say Windows NT? Long file and folder names seem to work fine on the Windows 2000 Workstation PC that I am using for testing purposes. If anyone can clarify this I would greatly appreciate it.

Dean,

You are correct that Windows 2000 in most instances does support long
file and folder naming (up to 256 characters).

However, prior to the current release of Servoy 2.1.2, we had a number
of developers who reported experiencing problems when creating a
database as a service on Windows 2000 - when the naming of their
database was did not follow the 8.3 naming convention required for
earlier versions of Windows.

Based on our subsequent testing to confirm the existence of this bug, we
added this note in the current documentation.

_____________
Marc Norman
Servoy

[Westy]

After some more testing on Windows 2000 Professional, I have found that short folder names are sometimes needed when running a bat file. At this point I am not clear on whether the short names themselves are needed or whether using short names is just fixing command lines that would otherwise be too long.

[Harjo]

We had a lot of problems with Windows 2000 server icm, with Sybase.
If you want to install the sybase services in a windows 2000 server, than pay attention to the doc's and name-conventionm or else it won't work!