Archive for the 'Bugs and Errors' Category
I create lots of reports for PeachTree accounting so I was surprise to learn that Sage has dropped the PeachTree name and is now calling the product Sage 50 Accounting. This change comes with the new (2013) version.
And just as they did in their last upgrade, they dropped fields from the tables. The first one I have found is one that some of my customers were using in their reports. The field is called PSQLCompletedDate and is (was) found in the JrnlHdr table. If you have been using this field in your reports you will probably need to replace it with the field CompletedDate, also in the JrnlHdr table.
I had a real mystery yesterday that cost me a fruitless half hour. I was trying to pass a shared variable from a subreport in Report Footer B to a formula in Report Footer C. I could see the value being stored correctly in the subreport, but the formula in RFC would not update no matter what I did. So I did some testing.
I had another subreport in the Report Header and it also had some shared variables. I could display those in RFC with no problem. So I knew that at least some shared variables were working correctly. Also, if I moved the original subreport to the RH, the variables started working. So I knew Continue Reading »
A Shared variable that refuses to work
Two different customers have contacted me recently because they were surprised to find a ‘new’ Crystal Reports feature in specific reports. They are usually puzzled as to why there is no way to make these features appear in ALL of their reports. Here are two examples:
- You go into File > Report Options and see an extra setting at the bottom that says “Convert DateTime Field:” and there are three choices: To Date, To Date-Time, To String.
- You go into the LINKS tab of the Database Expert and look at the properties of a join. There you see an extra section at the bottom with a check mark that says “Return all rows before joining” then below that you see:
When linking to two files from this file:
Look up both at the same time
Look up all of one and then all of the others
Look up all the combinations of the two files
Rather than being new features in CR, these are actually very old features, from Continue Reading »
Old reports with ‘new’ features?
I was troubleshooting a report that was taking a long time to get data from the database. The report used the same table configuration as many other reports, and none of those reports had performance problems. But when going in to check the links I noticed that there were two different connections. Then I got an info message from CR that said the report was using two different data sources, which was strange. So I went into “Set DataSource Location” and, sure enough, one of the tables was listed separately from the others, with a separate connection. The funny thing was that the two connections seemed identical. Same name, same properties, etc.
So first I took lone table Continue Reading »
Slow performance caused by a “split” DSN
When people enter date criteria they almost always expect to enter just the date value without times. But most modern databases use a DateTime data type rather than a date. If your data stores dates with times you have to be sure that you enter your date ranges correctly or you take chance of losing the data for the last day of the range.
The good news is that in most situations CR will make the adjustment automatically, but I found one situation where the adjustment doesn’t happen. Say you have a transaction date that is a DateTime field, and you are trying to select the transaction for January. You might go into the select expert and add a rule that says Continue Reading »
How CR adjusts date values for DateTime fields
All versions of Crystal Reports up to v12 (2008) need to use the 32-bit ODBC Administrator. But in Windows 7 you are taken to the 64-bit Administrator by default. A couple of years ago I wrote about this. Today after helping a customer I learned a few more strange things about the ODBC Administrator that can get confusing.
The user was creating DSNs but CR could only see the DSNs if he added it as a “user” DSN. If he added a new “system” DSN he could not see it. The odd part was that one existing system DSN DID show up in CR, but any new system DSN would not show up.
So the first thing I checked was that we were loading ODBCAD32.exe to add the new system DSNs. Then we recreated, reconfigured and retested the system DSNs. I also looked at the INI Files that ODBC creates and everything. So I was stumped. As I was telling them that I was giving up I checked the 64-bit ODBC shortcut I had added to my desktop. I was surprised to find Continue Reading »
Confusion over 32-bit and 64-bit ODBC
One of my customer sent me two screen shots. One showed a normal preview on his development machine. The other showed a preview window on the runtime machine. The second had the group tree, but the report was nothing but a long blank vertical strip. He had been struggling with it for a month and could not figure out what was causing the strange behavior at runtime.
When the preview behavior changes on a different machine, it is usually due to a printer driver problem. I also know that CR will normally Continue Reading »
Strange printer behavior at runtime
Last night I had a customer with a strange problem. Their report ran fine and looked great in preview and when printed. But if it was exported to PDF it had a long line down the page. This didn’t happen if it was printed to a PDF driver so the only time it was visible was when using the CR export function.
I opened the PDF and there was a vertical line on every page, even on blank pages, starting near the top. I opened the RPT and there was no visible object anywhere near the sections at the top where the object should be sitting. I was getting ready to start deleting objects one at a time to see if it was tied to a specific object, but first I decided to Continue Reading »
Mystery line in PDFs
One of my readers wrote in today to tell me that SAP released Service Pack 4 a few months ago. He had CR 2008 set to “Check for Updates on Startup” but it never triggered an update for SP4. Even after he manually clicked on “Check for Updates” the message said that he had the most recent version. But when he searched the SAP website he found it.
I have been holding at SP2 because of two issues that I wrote about earlier. But when I asked CR to check for updates I got the same message – that I had the most recent version. So searched the download site and found SP4 in the “Downloads” area of the SAP web site. I installed it and it didn’t break my dynamic parameters, so that is good news. The “Saved Data” issue was intermittent so I will be on the lookout for that or any new problems.
And thanks to Mark Edwards at DataReport Consulting for pointing this out.
On occasion I have worked with customers where the field explorer has become undocked and we have trouble getting it to dock again. I also remember clicking toolbar buttons and accidentally dragging the toolbar out of position, then not being sure how to get things back the way they were. So I was pleased to find a feature (tucked inside a little-used menu item) that will fix these issues. It is currently available in versions 11 through 14 and I assume that it will be available in later versions as well.
To use this feature go into the VIEW menu and select TOOLBARS. You will see a window that allows you to control which toolbars are visible. At the bottom is an option called “Reset all toolbars and explorers on the next restart”. Check this option and then close and re-open Crystal Reports. All your toolbars will go back to their default positions and your field explorer (and other explorers) will re-dock in their original positions.
Now I would have been even happier if this also reset the entire Formula Workshop. I have written before about the formula workshop disappearing, or the panels not docking correctly. Unfortunately these features are not currently reset by this option. So if you have these problems in the formula workshop you will still have to dig into the registry to fix them.