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=======================3 D= TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to rbase-l@rbase.com (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) =======================3D=======================3 D= TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to rbase-l@rbase.com In the message SUBJECT, put just one word: INTRO =======================3D=======================3 D= TO UNSUBSCRIBE: Send a plain text email to rbase-l@rbase.com In the message SUBJECT, put just one word: UNSUBSCRIBE =======================3D=======================3 D= TO SEARCH ARCHIVES: Send a plain text email to rbase-l@rbase.com 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=======================3 D=
