>>Let us know what you find,AE
Thanks, but I tried all your instructions and it didn't work.
When I take the subreport out of the main report, and then run with Logicity, it works fine. When I put the subreport back in, it doesn't work.
In fact after it prompts me for the password and then tells that it is incorrect (it's not!), it seems to send some kind of instruction back to the SQL database to lock it because if immediately after I try unsuccessfully to run it with Logicity and then open it in Crystal Reports it reports the password is bad because the database has been locked. It seems to unlock itself after a couple of minutes.
So not only won't Logicity run the report with the subreport embedded, it somehow fouls up the underlying database!
Any other suggestions? Sorry to be so much trouble but I am really hopeful getting this to work somehow.
Thanks for any other ideas.