Newsgroup: it.comp.lang.visual-basic
Titolo: Crystal Report

Caro Amici ho bisogno del Vs. aiuto.
Non mi funziona più bene CR.
Il problema è che quando voglio creare un nuovo report e seleziono il
database mdb su cui voglio lavorare, mi compare una strana richiesta di
password (l'mdb non ha password) alla quale sono costretto a rispondere con
il bottone CANCEL epoi compare il messaggio di errore "Database non
riconosciuto"
La ver. di CR è quella fornita con VB6
Spero nel Vs aiuto
Grazie

Ciao!
Non so se ho capito bene il tuo problema. Nonconosco molto CR se non x una
breve esperienza con CR8 qualche anno fa (esperienza che mi convinse del
fatto che CR non era cio' che faceva x me), ma visto che nessuno ti ha
risposto, vedi tu se ti puo' essere in qualche modo utile l'articolo che
allego in calce al mio post... sempre che tu non abbia gia' risolto.
L'articolo, in realta', e' di "seconda mano": l'ho trovato riportato in un
thread: 
http://makeashorterlink.com/?F38451679
Buon lavoro! :)
    Alex
New DAO350.DLL And Microsoft Access Open Session Prompt
Product: Crystal Reports Professional   Version: 7.0.1.192
Applies to: Not tested with other versions
Database: Microsoft Access      Platform: N/A   Date Verified: 9/23/99
 Problem:
 "There is a new version of the Dao350.dll (version 3.51.xxxx.x) that ships
with Microsoft Visual Basic 6.0 and the Microsoft Office 97 Service Pack 2.
 If this DLL has been copied and registered to a machine that does not have
all of the necessary supporting files for this version of the DAO, then
Seagate Crystal Reports (SCR) will give a MS Access Open Session dialog
prompt when attempting to create a new report, even though there is no
security on the database."
 Solution:
 "The problem is not with SCR.SCR will work fine with this version of the
Dao350.dll as long as all of the supporting files are there.  Other
applications will also fail, including Visual Basic's Visual Data Manager
().
 Copying to that machine the supporting VB 6.0 versions of:
 Expsrv.dll
 Vbajet32.dll
 Msjet35.dll
 May eliminate the problem, but it is better to ensure that all of the DAO
files needed for that version are present.
 From Microsoft's Kbase Article #Q192934:
 SYMPTOMS
 After installing a Microsoft Visual Basic 5.0 application on an end user's
computer, the run-time error 3447 is received when it is executed:
 "The Jet VBA file (Vbajet.dll for 16-bit versions, or Vbajet32.dll for
32-bit versions) failed to initialize when called. Try reinstalling the
applications that returned the error."
 This occurs when the application is created on a machine with both Visual
Basic 5.0 and 6.0 installed and the setup program for the Visual Basic 5.0
application is created using the Visual Basic 5.0 Application Setup Wizard.
 CAUSE
 Visual Basic 6.0 installs new versions of the DAO and Jet files on the
development computer. The version of Vbajet32.dll (6.1.8167) that comes
with Visual Basic 6.0 is dependent on Expsrv.dll, but the Visual Basic 5.0
Setup Wizard does not include this file because it is not included in the
dependency information in Vb5dep.ini.
 RESOLUTION
 You can attempt to work around the problem by adding Expsrv.dll in the
File Summary screen of the Setup Wizard. However, you may run into problems
distributing other updated components as well.
 Following are the safest alternatives:
 Develop and create setup files for your Visual Basic 5.0 application on a
"clean" computer.
 -or-
 Upgrade the application to Visual Basic 6.0 and create the setup files
using the Package and Deployment Wizard (PDW). "
KBASEID: C2002274