Database Username & Password Help?
I have just downloaded the crystal corral software and it looks very good, but after adding my first report and then clicking on it, it has asked me for my database username and password, which i typed in but it will not accept it, i know it is correct because i use it on a daily basis for other reports! Any help would be appreciated. Thanks AJ.

i managed to get it working now, i needed to change a few settings in my ODBC drivers, and now it works fine, stunning piece of software.

Database Username & Password Help
What is the solution to this? Because I'm having the exact same issue now. Fiona

Yes, please, I'm having the same problem so what is the correct solution?? I can't see to tweak my ODBC settings in the right way :cry: Thanks J

Password for logging into Database
Hi, I too am having this problem. Any help with logging into the database would be very helpful. I am the domain admin, and have tried every way I know to log into my database from this program and it just doesn’t work. I have set up user, system and file obdc connections as well, and nothing. Any help would be appreciated, Trent

Trent, I'm no tekkie or engineer but spotted our reason for this error message ... On our large network, some report definitions are saved to a shared network folder, which was mapped as G:\ on some workstations and L:\ on others. They are then run via workstations via Coral. I spotted that some workstations didn't get this error and the drive mapping was the reason - because it differed from the workstation on which the report was defined. Aligning drive mapping to match the workstation on which reports were defined (using Crystal Reports) completely solved the problem! I hope this helps you - and anyone else with this error. J :)

Hi J, THanks for the post, but I actually copied the crystal report to my local desktop to test, and today after reading your post I went into crystal and looked around for the "mapping" that may be stored and didn't see anything. I really feel it has something to do with the ODBC connection that I have setup on my machine, but I could be wrong. It would be nice to know exactly what the program is attempting to do at this point, because the error and log in screen are deceiving. I may install this on a non-vista machine and see if I get different results. Could it possibly be some stupid vista security issue? I installed another viewer to test out and I am getting the same error now as well. I believe that was from logic city. Who knows! If anyone else has some insight I am all ears. Thanks, Trent

Hi again :o) Reminder ... I'm no tekkie so pardon the dippy language! The mapping I'm referring to only matters if you are on a network. The mapping is not a setting within Crystal or Coral - it is a "feature" of how your network has been designed. I hope I'm not teaching you to suck eggs or insulting your intelligence about this - I just dunno whether you know about mapping etc. If you are on a network and would like me to help you explore this, post a reply and I'll tell you where to look ... but PLEASE don't get offended it this is very basic and I am teaching you to suck eggs. J :)

No egg sucking over here:) Seriously, yes I know what drive mappings are, I am a IT manager, so tekie for a lack of a better word. I am not however an expert in crystal, so that explains my question about a setting in crystal that I am missing. We do use mapped drives, but like I said I moved it to my local PC and it didn't work, it also didn't work on a mapped drive. I was hoping that you had found something in Crystal that you changed that made this work. No worries, I am sure someone will figure it out. I have spend enough time on this, I could have purchased a pay product by now, but i really would like this to work, plus help promote it to the other 1000 users that I deal with in our user group for our ERP software. I could make this guy famous if he helps me to get this working... Please help Groff!!

Possible solution to username / password prompt
I also had this problem, and it was due to a bug in Crystal itself. If you use a System DSN for database connections, Crystal Reports sometimes swaps the Database Name for the Server Name, resulting in an incorrect connection. It only seems to affect certain machines on our network, which is very odd. To get around it, I created a file DSN on the server, and modified the report to use that with a UNC path (i.e. \\servername\folder\etc\dsn_name.dsn). You could also use a connection string in the report. We're using Crystal Reports XI, but it wouldn't surprise me if this bug was in other versions.