Re: Status 11 and 12 with PSQL 9.1
- From: "Bill Bach" <goldstar@xxxxxxxxxxxxx>
- Date: Sun, 06 Nov 2005 22:00:40 -0600
Your application is uaing an old method of defining the data file names
-- using a SPACE as a terminating character.
Since OS/2 created on the ability to have long file names (and this
feature has caught on with almost every other major OS), the space
terminator is no longer "safe".
You have two options:
1) Change the code to terminate every filename with a NULL byte (0x00)
instead of a space (0x20).
2) Change the "Allow Embedded Spaces" setting in the PSQLv9 PCC to
UNCHECKED (i.e. OFF). This will force PSQLv9 to behave like older
versions that did NOT allow spaces to appear in filenames.
Please note that if you pick option 2, you must change it on every
client workstation.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***
Axel Potthoff wrote:
> Hi,
>
> when I install PSQL 9.1 to a new System and start our application, I
> got Status codes 11 and 12.
>
> When I install PSQL 8.x to a new System and start our application,
> everthing works fine.
>
> When I install fist PSQL 8.x to a new system and after this install
> PSQL 9.1 to this system and then start our application everything
> works fine too.
>
> Can anyone tell me, why simply installing PSQL 9.1 does not work?
>
> Our application uses simple Btrieve calls and has no SQL features.
>
> Thank You
>
> Axel
.
- References:
- Status 11 and 12 with PSQL 9.1
- From: Axel Potthoff
- Status 11 and 12 with PSQL 9.1
- Prev by Date: Avoid overwritting other's data?
- Next by Date: Re: Avoid overwritting other's data?
- Previous by thread: Status 11 and 12 with PSQL 9.1
- Next by thread: Avoid overwritting other's data?
- Index(es):