Formula field is in use 1

[WeirdScience]

Hello people,

In the company I work, we have a problem running a certain Crystal Report.

The report works at some computers and not at others.

When I try to open the report, I get several errors:
- Formula field is in use: XXXXX, count = 1
- Database field has not been deleted: XXXXX, use count = 1, hold count = 0

Can anybody point me in the right direction?
I've already took a copy of the folder c:\windows\Crystal and copied that to my own pc.

Regards,
WeirdScience

--------------------------
Foxpro.. Why-oh-why?

 

[Madawc]

Try Database > Verify Database on one of the computers that can open the report.

Also File > Export using Report Definition might let you track down the formula field that is giving trouble.

If you do find it and can't work out the problem, pleased paste it here.

It helps to give your Crystal version - 8, 8.5, 9, 10, 11 or whatever. Methods sometimes change between versions, and higher versions have extra options.


Madawc Williams (East Anglia, UK). Using Windows XP & Crystal 10

 

[WeirdScience]

Hello Madawc,

I'm gonna try this.

Thank you in advance anyway!

Concerning changing to other versions: Yes, you're right. But since we're changing our whole IT-structure, we wait until this has been done.

Regards,
WeirdScience

--------------------------
Foxpro.. Why-oh-why?

 

[WeirdScience]

Hello Madawc,

I'm starting to think it's linked to (missing or unregistered) DLLs, because I have now another report which won't run on my computer.
Can anybody tell me how to investigate which DLLs are used in certain reports? Without have the possibility to open the report.

The only link between these 2 reports is that there is a graph used in these reports.

Regards,
Guido

--------------------------
Foxpro.. Why-oh-why?

 

[Madawc]

Sorry, I don't know about dlls. SOmeone else would need to advise you (and knowing the version would help)

Madawc Williams (East Anglia, UK). Using Windows XP & Crystal 10

 

[WeirdScience]

Hello Madawc,

Yesterday I've found the problem. The cause was indeed a Dll which was 'out-of-date'. I needed to copy the pg32.dll from a desktop which the report was working to the desktops where the report was not working. This did the trick.

Anyway: Thanks for answering!!!!

Regards,
WeirdScience

--------------------------
Foxpro.. Why-oh-why?