Search results for query: *

The CLIENTNAME environment is set to "CONSOLE" on some xp workstations after they have had a thin client session running. I'm not sure why this happens, and only on some workstations (could be version of XP?), so I've put this in to overcome this problem. I have my fingers crossed...

I use the following VB to do this... If Trim(Environ(&quot;CLIENTNAME&quot;)) <> &quot;&quot; And UCase(Trim(Environ(&quot;CLIENTNAME&quot;))) <> &quot;CONSOLE&quot; Then MsgBox Trim(Environ(&quot;CLIENTNAME&quot;)) If the client is running TS, then the clients machine name is returned.

We experienced this problem when our SQL backups were failing due to file locking problems on the server, solved by deleting the old backups. You might also want to try increasing the number of transaction backups if this doesn't work.

The BSETUP of the past seems to have been replaced with the Pervasive Control Centre. If, like me, you are using this from DOS and do not have easy access to the PCC, then I reccommend editing the BTI.CFG file in the servers SYSTEM directory. Hope this helps.

I've encountered this problem several times, which was due to an old version the BREQUEST.EXE lurking about, the upgrade program does not always seem to remove them, especially if you're using Novell. Do a complete check on both the server and workstation for the BREQUEST.EXE and check the...

I did a bit of checking, assuming that the error is not being caused by data corruption, increasing the Active Clients settings should solve this problem. I used the following setup to do this in Pervasive 7. 1. Click Start, Programs, then Pervasive SQL 7. 2. Select Configuration (Setup) from...

According to the Pervasive spec, Error 214 occurs when a user has Alter rights to a table and has rights to every column in the table. I'm not 100% sure what this means, but you could try revoking access to the table before making changes to it, and then regranting access afterwards. If you...

I find the Pervasive GUI is a bit of a nightmare as it's so different to the previous versions. Try editing the BTI.INI directly and this should help.

I've found that the BUTIL.EXE utility is the best way to recover files. From the DOS prompt type the following to recover the file CORRUPT.BTR: BUTIL -CLONE CORRUPT.NEW CORRUPT.BTR BUTIL -COPY CORRUPT.BTR CORRUPT.NEW REN CORRUPT.BTR CORRUPT.OLD REN CORRUPT.NEW CORRUPT.BTR The first line...

Thanks for trying this, I suspect it's a problem with my RDBMS.&nbsp;&nbsp;As a test removed simplified the statement to:<br>SELECT *,<br>CASE WHEN (Datafield &lt; 0)<br>THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;52755 <br>ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;12785<br>END NewDatafield<br>FROM tbltest<br><br>I'm...

Thanks,<br><br>I've tried to include this into a SELECT statement, but I'm getting an invalid statement error. Any ideas?<br><br>SELECT <br>CASE WHEN (datafield &lt; 0 )<br>THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;datafield + 52755 <br>ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;datafield - 12785<br>END<br>FROM...

A large group of us have looked into this one before.&nbsp;&nbsp;It seems that the Interrupt Vector is coded into the software not changeable.&nbsp;&nbsp;Our solution was to change the other software accordingly.&nbsp;&nbsp;Hope this helps.

We have completed this upgrade and it worked fine, but performance did suffer.&nbsp;&nbsp;Upgradeing Btrieve 6.15 to Pervasive.SQL 2000 seemed to solve the problem.

I have an application that, due to Y2K and other issues, stores dates in an unusual format.&nbsp;&nbsp;To read this data as number of days since 01/01/1900, negative values must be added by 52755 and positive values must be subtracted by 12785.&nbsp;&nbsp;I am trying to create a VIEW the will...