I use Crystal w/ in Multiuser 6.5++ db using Oterro.  Works great.

You have to get Oterro set up first.  I found the best way to do it is to
set it up and test it w/ Excel.  Once that works, Crystal should not have
any problems.

If you have an owner pw on your database, that needs to be in the username
field.

I may have detailed instructions from an old conference.  I will look and
see if I can find them.  I think they may be buried on my website somewhere.
--- Found it   
http://sosamon.com/rbase/conf_2002/presentation.doc
Also download all of the files in the directory
http://sosamon.com/rbase/conf_2002 
for you viewing pleasure

I actually set up Crystal reports so you could call them from R:base passing
parameters on the fly for the report.  That is what the rdc_pass.exe is for.


Troy


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Steven
Hoggan
Sent: Tuesday, July 05, 2005 8:07 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Problems getting Crystal Reports for VS2003 to
speakto my 6.5++databases

David,

Tried with my test database and also with Bluzvan (which I forgot to
mention worked fine for me with CR previously) connected separately with
Multi On.

Both failed.  I was presented with a dialog box which displayed the
target database in a combo box called "Server name", together with
additional text boxes in which I was prompted to enter the database
name(?!), the user name and the password.

Seems your diagnosis is bang on.  Now, how to setup CR to access
databases in multi-user mode.

Thanks for the input.

Steven


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of David M.
Blocker
Sent: 05 July 2005 14:58
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Problems getting Crystal Reports for VS2003 to
speakto my 6.5++databases

Steven

Is this the first time you have tried to connect with Crystal Reports?

If yes, on that test database you set up, try connecting to it in R:Base
with MULTI ON and then try printing the Crystal report again which you
were successfully able to print when you were the ONLY one using it. I
suspect it too will fail.

If so, then the issue centers around somehow Crystal expecting to be the
only one in the database...

Others out there who have actually used Crystal with R:Base, chime in?

David Blocker
[EMAIL PROTECTED]
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261
----- Original Message -----
From: "Steven Hoggan" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Tuesday, July 05, 2005 8:20 AM
Subject: [RBASE-L] - Problems getting Crystal Reports for VS2003 to
speak to my 6.5++databases


Hi all,

Hopefully someone will be able to quickly point out the error of my
ways.

Using 6.5++ for DOS, Oterro 2.6, Visual Studio.net Professional 2003

We have a number of VS apps that quite happily access my databases day
in/day out using a DSN-less connection (no password, no userid) along
the following lines

"Driver=Oterro Database Driver (*.rb1);DBQ=H:\PATRECS.RB1"

I only have one OTERRO.CFG file on my machine and no other OTERRO.CFG
file to be found on either of the network drives on which my databases
are located or anywhere on my machine search path.

When accessing an existing database locally, I successfully set up a
connection to the database using the ODBC(RDO) option within the CR
Reports Wizard.  It does ask for username and password, but there has
never been one applied to the best of my knowledge, so I skip their
entry.  I can, however,  successfully access the tables/columns in the
database and set up the basic report.  At print time, however (the print
is nothing more than the display of a simple form with the CR Report on
it - there is no custom SQL at this point, only the selection of fields
from the Wizard), I receive the message "failed to open a rowset".

Now....when I try to access one of our existing databases on the
network, I receive a message that the database is inaccessible and is
probably open with MULTI set OFF.  VB.net and VBA never have problems
connecting to the database.  The database is, certainly, open in
Multi-user mode, but given that our VB and VBA apps access the database
constantly in multi-user mode, I'm not sure where to start digging with
this one.

It would appear that it is very much a "settings" issue.  My problem is
that I've never (slap on the wrist time) consciously applied any
userid/password grant/revoke security on any of our databases, so I'm
not sure where to start in trying to set/reset them.  All of our apps
handle security access entirely through the app and tables in the
database indicating the tables the user does/does not get access to,
together with the level of access.

I've unloaded the structure of the existing databases and compared it to
the new ones I've created.  I can't see anything different between
either that suggests userid/password/settings issues.

Finally, and this is probably the biggest clue to the culprit, I can
create a new database (no passwords/user info/anything special) and
happily attach a simple CR report to it and print the report from my
app.

Hmmmph!!

Our existing databases (5 production databases at the moment), while not
massive, are generally in the 300/400MB region each and the notion of
porting the data from an existing database into a newly created one is
one that fills me with absolutely no enthusiasm.  One further point is
that all of these databases have been successively upgraded from version
3.1, and that may be the root of the problems.

I'm hopeful there is a simple database settings solution to this one.

All/any ideas greatly appreciated.

Many thanks in advance,

Steven





Privacy & Confidentiality Notice
-------------------------------------------------

This message and any attachments thereto is confidential and intended
solely for the person to whom it is addressed.  It may contain
privileged and confidential information.  If you are not the intended
recipient you must not read, copy, distribute, discuss or take any
action in reliance on it.

If you have received this information in error, please notify us as soon
as possible on the telephone number shown.  Thank you.  Fitzpatricks.

Tel:  +44 (0)141 306 9000
Fax:  +44 (0)141 306 9090
Web:  www.fitzpatricks.co.uk

--- RBASE-L
=======================3D=======================
D=
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)
=======================3D=======================
D=
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected] In the message SUBJECT, put
just one word: INTRO =======================3D=======================
D=
TO UNSUBSCRIBE:
Send a plain text email to [email protected] In the message SUBJECT, put
just one word: UNSUBSCRIBE
=======================3D=======================
D=
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.
=======================3D=======================
D=

--- 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