Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Active-X problem with CE 8.5

Status
Not open for further replies.
Hi,

Not sure if it is related but some of my users experience issues upgreading and implementing the Activie X browser. Users were experiencing similar symptoms to those outlined but I don't think it was related to date parameter reports.

We went from C.E. 8 to 8.5 recently and I had to seek out the Crystal Report Viewer Control under the downloaded program files directory in NT/XP and delete this file. The next time the user attempted to access a report, it forced them out to the Crystal site to get the upgrade and all seems to be working fine now.

Paulos
 
Thanks for the response.

I just learned that this IS an official bug, CD was able to replicate the problem.

Some XP clients will hang if a DATETIME is the very first prompt.

I'll post again when it's resolved.

-k kai@informeddatadecisions.com
 
Nice to know... some of our desktops will be moving to XP. I will rearrange parameters so the first one isn't a datetime.

What happens when the first paramter isn't a datetime but the user never sees it? I am thinking ahead to what to do if all the parameters are datetime.. a "dummy" parameter that the user never sees...

Thanks for the heads up.

Lisa
 
You'll get prompted for the dummy anyway.

There are very odd behaviors associated with datetimes, especially if you try to NOT prompt for parameters when a datetime is in the list.

The datetime just isn't handled correctly, I suspect a patch is in the making.

-k kai@informeddatadecisions.com
 
You can make parameters that the user never see's. I use them a lot. Just set the default and don't click the "Prompt the user for new value(s) when viewing " box.

Lisa
 
Ahhh, I see, you mean if I place a parameter first that isn't used within the report. Interesting idea, I'll try it on Monday.

I did try placing a parameter before the datetime which is used in the report, and then turning off the prompt for within CE85, it ignores and prompts for it anyway. Hence the previous post of:

"You'll get prompted for the dummy anyway."

I understand that it shouldn't prompt, but it does...

I've also isolated some odd behavior with datetime under Win2K, once I complete my testing and submitting to CD, I'll post here, with solutions, if there are any.

Why do you use parameters that the user never sees a lot?

-k kai@informeddatadecisions.com
 
I use paramters that the user never see's for creating dynamic SQL in SP's. I have multiple databases that have multiple matching DB's. For example I have DB ProdMain which also has data in ProdSub1 that is from a related, but stand alone application. They talk to each other enough to keep their keys in sync. Now I also have databases Test1Main, Test1Sub1, Test2Main, Test2Sub1 etc. If I can pass the name of the correct sub database to the SP I only need to write the SP once. Then all I have to do when I want my report to change which database it is pointing to is to set the location of the Main db. I then set the sub default in Enterprise and don't prompt the user for this info (they wouldn't have the foggiest idea what it is anyway).

Lisa
 
I see, sounds clevah ;)

Probably a bit nightmarish to maintain, and you lose some performance due to dynamic SQL, but it sounds fun ;)

I always seem to end up writing SP's at a more atomic level, I've toyed with similar ideas, but I've never implemented.

-k kai@informeddatadecisions.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top