Generating a Pictoral Directory

[ehitomi]

We would like to generate the Standard, unaltered Pictorial Directory from the Family Mailing List Report Menu. Families were entered using Integrated Data Entry and on the Picture Tab of the Family record we imported JPG images of the family. We have verified that they display correctly on the Picture Tab and were stored in the Picture Folder within the data file within PCPLUS10 folder. There are no pictures on the Individual profiles.

We select the Pictorial Directory from the Family Mailing List Reports Menu, All Mailing Codes on the Selection Criteria screen, and on the Report Option screen we select all status' and UNCHECK Only Include Families With Pictures (because about 10% of our families do not have pictures, but need to be in the directory) When we generate the report, we get several error messages followed by the populated report.

The errors we receive are:
Error: 1444
Method: setup
Line: 22
Message: Type Library C:\PROGRAM FILES\SEAGATE SOFTWARE\REPORT DESIGNER COMPONENT\CRAXDRT.DLL not found

Error: 2061
Method: setup
Line: 23
Message: Index or expression does not match an existing member of the collection

Then the Error 2061 again for Line 26
Then the Error 1444 again for Line 34
Then the Error 2061 again for Line 35, 38 and 39

When the populated report is generated, we get all the correct families listed – however those that have pictures on their Picture Tab have a Stock Clip Art image of a black camera and the words “Picture not available.” Those families that do not have a picture on their picture tab have a blank space where the picture would have been.

Does anyone have any idea how to get the pictures to appear on the report? And what we are doing wrong?

We are running Powerchurch 10.4 - Program Date 7-14-2009 on a 64 bit Windows Vista machine with full administrator privileges. We have verified our data, and the computer is up to date with all Windows and software updates.

Thank you for your expertise – we are at a loss as to what to try next

[tborgal]

Doing some checking I have run into the same errors in both V10 and V11 on a Windows 7 64 bit machine. Works fine on my XP machine. Do we have a problem with 64 bit operating systems??

[NeilZ]

According to a post by Zorak, in the Windows 7 topic, 64 bit should be fine.

The error shown:

Message: Type Library C:\PROGRAM FILES\SEAGATE SOFTWARE\REPORT DESIGNER COMPONENT\CRAXPRT.DLL not found

shows that a .DLL is not in the directory C:\PROGRAM FILES\SEAGATE SOFTWARE\REPORT DESIGNER COMPONENT.

On my XP laptop, this is the only file in that directory. I'd check to see if it is there. I've not yet installed Windows 7 32 bit on my Pentium 4 desktop, I'll try that tomorrow and see if that problem turns up.

[tborgal]

OK that resolves the problem. I should have figured that out on my own. How and when does this file get created? When running the report from a networked machine you need to have the file resident on that machine or you get the error. That is why I got the error on my Windows 7 machine. Is this mentioned anywhere in the manual?
Another lesson learned. The problem is retaining it.

[ehitomi]

When we first received the messages about a missing .dll - we did check to Report Component Folder to see if the file existed - it did. There was one item in the folder and it was named correctly - the difference being that the message had everything in uppercase and the actual file was named all in lower case - but that should not have made a difference.

We did do a clean install of the application and reapplied the maintenance updates - and the .dll file was there - and we still get the message that it is missing.

We then removed the .dll file from the folder - forcing the system to regenerate it in its "one time process" - and it was recreated. The message still appears saying that it is missing.

I do not know what else to try.

[Zorak]

What's happening here is that when the Crystal Reports files are being installed, 64 bit Windows is putting them in the Program Files (x86) folder, which is correct. Crystal Reports is throwing the error because it is looking in the regular Program Files folder.

The odd thing is this is very inconsistent behavior. We have installed for testing purposes on 64 bit machines and never been able to recreate the issue. But, we have what seems to be about one customer per month report this error. We can't find any thread between those that have the problem and those that don't.

The simple solution is to copy the Seagate Software folder out of the Program Files (x86) folder and paste it into the normal Program Files folder. This has fixed it for everyone we have talked to.

[tborgal]

Thanks Zorak,
I found the files in the x86 folder as you said. Very interesting problem.

[NeilZ]

Thanks Zorak,
I found the files in the x86 folder as you said. Very interesting problem.

Which is why many businesses are still on XP, something always seems to break when M$ does an 'upgrading' of its OS.

[ChRLee]

I am running Window XP Professional and am running into the same problem. I can not find a Program File (x86) with the file in it. I believe my issue is because my hard drive is h:/ instead of c:/, is there a way to change which drive the program looks in for this file?

Angie

[Zero]

Thanks Zorak,
I found the files in the x86 folder as you said. Very interesting problem.

Which is why many businesses are still on XP, something always seems to break when M$ does an 'upgrading' of its OS.

This isn't actually an issue specific to x64, it was just easier to find on a x64 machine.

Either way, the issue has been fixed and will be available in the next maintenance release.

For now, the fix is to copy the Seagate Software folder into the normal Program Files folder as stated earlier.

[Tracy]

Thanks Zorak,
I found the files in the x86 folder as you said. Very interesting problem.

Which is why many businesses are still on XP, something always seems to break when M$ does an 'upgrading' of its OS.

This isn't actually an issue specific to x64, it was just easier to find on a x64 machine.

Either way, the issue has been fixed and will be available in the next maintenance release.

For now, the fix is to copy the Seagate Software folder into the normal Program Files folder as stated earlier.

I found a reference directly to C: in the code. This has been changed, but won't be available until the next maintenance release. We apparently started with some test code that got put into production.

[ChRLee]

Thanks Tracey, but when will the next maintenance release be available? I need to print a directory before the end of the year for my church and can not at this time due to this code that needs to be updated. What do I do in the mean time?

Angie

[Zorak]

For now, the fix is to copy the Seagate Software folder into the normal Program Files folder as stated earlier.

As mentioned earlier, the fix is to copy the Seagate Software folder from the right location into the wrong location.

In My Computer, copy the "H:\Program Files\Seagate Software" folder to "C:\Program Files\Seagate Software".

[ChRLee]

Zorak,
Again, I can not copy it to the right location in C: drive because that computer does not have a C: drive. I can not copy it to somewhere that doesn't exist. Do you have any other suggestions?

Angie

[Tracy]

The latest release of the 11 beta should have this fix already. See if you can still get in.
http://www.powerchurch.com/forum/viewto ... f=1&t=4055