1. My build is 3.50.10.30807

2. Created time and date of oterro.dll is 9/14/2006 2:10:06 PM

3. Scratch setting is TMP

4. I have unlimited license.

5. I am using R:Base 7.1

6. I am not sure what you mean

7. I use ODBC connections

8 and 9 I use ASP

10. I turned on debug and it does not show anything strange.

Is there anything we should to to convert the database from rbase to
oterro??

Dan Goldberg

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of A. Razzak
Memon
Sent: Wednesday, November 08, 2006 10:40 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Problems using Oterro 3.5 ODBC from IIS & PHP


At 12:24 PM 11/8/2006, Radi Shourbaji wrote:

>We're using the Oterro 3.5 ODBC drivers to access an
>R:BASE database from a PHP application running under
>Windows 2000 / IIS5.  Periodically it seems that the
>a query will hang, and eventually lockup IIS requiring
>a restart.  The problem seems to be aggravated when
>multiple requests are issued to R:BASE via Oterro.
>So I was wondering:
>
>1) Is there a way to set a timeout to force the request
>    to terminate and return to PHP / IIS if it takes
>    longer than X seconds?
>
>2) In case its a license count issue - is there someway
>    to query Oterro (via ODBC) to check the number of
>    licenses currently in use?


Radi,

A few questions and suggestions related to PHP, Oterro
and R:BASE:

01. What build of Oterro 3.5 are you using?

     Start | Programs | Oterro 3.5 | Check Version ...

02. What is the exact date and time of Oterro35.DLL

     \WinNT\System32

03. What is the setting for SCRATCH in Oterro35.CFG

     \WinNT

04. What is your license for Oterro 3.5?

     Limited User License or Unlimited

05. What version of R:BASE?

06. Does the settings for Oterro35.cfg match the
     settings of R:BASE configuration (.CFG) file in path?

07. What kind of Server Connection are you using with PHP?

     Persistent or ODBC Cursor

08. What is the exact version of PHP?

     Version 5.1.6.6 or ???

09. Are you using PHP as Module or CGI?

     PHP 5.x works well with R:BASE/Oterro 3.5 as CGI.

10. Do you know how to create the Oterro Debug log?

A a registered use of our CURRENT products, I suggest
that you send all details with supporting material and
samples to:

. mailto:[EMAIL PROTECTED]
   or
. mailto:[EMAIL PROTECTED]

Did you know that R:BASE Technologies has been using
PHP with Oterro and R:BASE since the inception of our
own R:PHP?

PHP is the ONLY language used at RBTI and all our WEB
development projects for our clients.

The entire site (rbase.com, rwebsuite.com) and all mini
sites are powered by R:WEB Suite, fully integrated with
Apache, PHP, R:BASE and Oterro.

A few published and public sites powered by R:BASE,
Oterro, Apache and PHP:

. http://www.rbase.com
. http://www.rbase.com/bluzvan_Oterro35
. http://www.rbase.com/bluzvanWithStyles
. http://www.rbase.com/property
. http://www.rbase.com/getproperty
. http://www.rwebsuite.com
. http://www.rwebreports.com
. http://www.rwebreports.com/dynamicreports
. http://www.rupdates.com
. http://www.razzak.com/fte
. http://www.razzak.com/sampleapplications

Very Best R:egards,

Razzak.

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
================================================

Reply via email to