Search results for query: *

Okay I got this one now. I needed 'DATE()'.

Yes. That was it. Don't know why it was in there. I found a note on MS knowledge base that said VBA won't compile if there are any MISSING references, so I unchecked and that error is gone. I still have one error left - the date issue. I want to default a Date field in a form to the...

I'm getting same kind of error. I developed an access app/db on Win2K Office 2K pro. It has trouble running on a Win XP machine running Office XP. I have found one object library marked MISSING: shappmgr 1.0 Type Library. The module for this is C:\WINNT\System32\appwiz.cpl - control panel...

Sorry. I meant CCM. I have seen the errors you're experiencing when upgrading from 8.5 to 9.0. I worked with BO tech support for awhile with little success. Applying sp1 made it worse. I finally formatted the box and installed CE9 from scratch. Applying CE9 SP1 disabled the services, which...

I have used Suzannes's method to find field references. As or the date parameter, we ran into this also - we want to be able to schedule a report everyday with yesterday's date and ba able to schedule the same report and pass a date. So we use stored procedures and schedule with a dummy date of...

Check in the CMC that all the servers are enabled. Seems to me that SP1 disables some of the servers.

I ran into this when upgrading from CE8.0 to CE 8.5. The import utility doesn't bring the profiles. So here's what I did. 1. Ran a custom CSP against the old system database to show the profiles. 2. Saved this off to a database. 3. Ran another custom CSP against the new system database using...

Thanks Tony, I believe I've got all those. If I change the background color in the detail section, I can see that color on the second (erroneous) page. I have tried to change the width of the detail section section to no avail. I'll try your suggestion when I get back at it tonight. Thanks...

I'm having the same problem. The report was originally designed landscape, but I've removed many columns and it now fits into portrait. The report grid continues to be out at 9". I drag it to 7.5 and it snaps back to 9. There are no controls even close to 7". I have tried changing width to...

The correct tool is the 'Import Wizard' in CE 8.5. Don't bother trying to use it, if you haven't applied the latest patches - early versions had bugs. It will import folders (friendly name and all) and instances (look for the check box on the target APS specification dialog). Lots of...

If the 100+ reports are already published in CE 8.0, you can migrate them to the 8.5 aps using the migration wizard.

Has anyone else experienced performance problems when querying the APS? We've written some csp code to look for instances of reports that meet certain criteria, so we don't have to drill into each report looking for things like failed instances. This often puts the CrystalAPS service into a...

Use the Crystal Management Console. Go to the report. Select the database tab. Enter the username and password and click on the Update button. You also give any parameters default values from the parameters tab. Be sure to hit the Update button BEFORE moving to different page or the changes...

I know this isn't related to your problem, but the native driver database logon/password can be set when you publish the report. This way the users don't get prompted. We use this method - it works fine. We use the same db connection for all subreports.

Do all your reports act this way, or just this one? Have you tried a different Oracle driver, like a native driver? Are you using the ODBC driver for a specific reason like to display images or maybe 9i requires a newer OCI?

When you look at the metrics for the Report JobServer, do you see something like this?: Processing Mode: Launch a subprocess (Job Server Child) for every request.

Try increasing the the number of Job servers: CMC; servers, <yourreportserver>.report. If it shows 1, increase it to 3.

How about contacting Crystal tech support?

I've been told by crystal decision's support folks that this part 'Info: assert failure (Y:\backend\jobserver\dlls\procreport\src\reportdllerrors.cpp699).' is the path their developers use for debugging and should be ignored. Typically print engine errors have something to do with failure to...

How long do you suppose that will be?