Forgot password? | Forgot username? | Register
  • Index
  • » Users
  • » gambleb
  • » Profile

Posts

Posts

20-Apr-18 23:43:41
Category: Using EMu

Hi Barbara,

Here at NMNH we are using a rather old version of Crystal, Crystal Reports for ESRI version 11.0.0.893.  We also have used a Crystal Reports 2008 Developer version 12.0.0.683.  We only have limited licenses for the 2008 version.

I believe the crystal viewer app that installs with EMu is actually from an older version.  Perhaps 11.  I know we inquired about upgrading it but apparently later versions of Crystal have different deployment licensing issues for the viewer if I understood Axiell's response correctly.

Beth :-)

22-Jun-16 02:57:44
Category: Using EMu

Very ingenious method.  I'll stick with my texxmlreplicate method but love knowing there is a crystal only way to handle it.

Beth :-)

20-Jun-16 22:21:35
Category: Using EMu

Very interesting Bill.  Would you be willing to elaborate on what is in the Read Only CSV file that enabled the duplication?  Do you have to recreate this CSV file each time for different data sets?  You have peaked my curiosity ;-).

Beth :-)

09-Mar-16 00:33:23
Category: Using EMu

Hi Bill,

Yes but there is some behind the scenes stuff that has to be done.  Axiell created a method for doing this by creating a custom report type based on a program they wrote called texxmlreplicate.  Either Axiell staff or someone with scripting expertise at your institution will have to create a very tiny script calling this program which tells it what field you wish to use for the number of duplicates.  What the program essentially does is to duplicate the data row the number of times specified in the field.  I gave a presentation on this at 3rd North American EMu Conference in NY.  The presentation is called Unleashing the Dark Crystal – Crystal Reports.  You can find a link to this presentation in the EMu Conference page.  We now have about three different custom Crystal reports in our system based on this method and they work pretty well.

Good luck and let me know if you need any further guidance.  I would contact your Axiell support staff for assistance setting things up.

Cheers,
Beth :-)

25-Feb-16 00:52:47
Anyone using the Insurance Module?
Forum: Catalogue

Hi Karen,

We use the insurance module but in relation to our transactions.  We have the insurance module linked to our custom transactions module and our movements module (we call shipments).  We record the insurance policy information, who pays for it, status (active or expired), type such as wall-to-wall or transit only.  We don't record claims.  Our insurance is actually managed by a central Smithsonian office and not at our museum level information about the activity on the policy is managed elsewhere.

This does not equate to the way you are using the insurance module. In its current state the module does not appear to allow you to link specific claims history to specific objects unless you created individual insurance records per object, or individual insurance records per claim and ignore the claim history as you mentioned.  Both of these options sort of defeats the purpose.

Sorry my response isn't more helpful ;-).

Cheers,
Beth :-)
NMNH - Smithsonian Institution

06-May-15 22:03:25
I'm trying to display the value of a single row from an embedded table in the Requests...
Category: Using EMu

If you do it via the select expert then you can use the summation formulas in Crystal because the other rows are not present and therefore don't factor into the calculations.

Good Luck!

05-May-15 23:36:20
I'm trying to display the value of a single row from an embedded table in the Requests...
Category: Using EMu

OK, there are a couple of things that may be the problem.  When including fields in your report that appear in a grid in EMu you should ALWAYS group them together so they get put into their own .csv file and the rows and column data will stay together.  For these multi valued fields are you converting them to text via the table to text option in EMu report settings?  If so, don't do that.  That will put all your values into one atomic field value and you would have to manually parse out what you want in crystal via a formula.  Instead group the different field from the grid together using the group feature in EMu report settings.  Don't include the groupname.csv file in your main report.  It should be in the subreport only.  Don't include the modulename.csv file (master csv) in the supreport.  The subreport linkage will be on the shared key field.  In your subreport use the Select expert to add the filter for "Image Field."  If this doesn't work, attach your .rpt file here so I can have a closer look.

Beth :-)

30-Apr-15 01:12:22
I'm trying to display the value of a single row from an embedded table in the Requests...
Category: Using EMu

Hi Foy,

What you want to do is in the Subreport for the Costs you want to use the Select Expert (Report menu - Select Expert menuitem) and add (click <New>) a Selection for the ImgExpla_csv.ImgExplanationOfCost is equal to "Image Fee".  This will exclude rows that aren't Image Fees.  Hope that helps.

Beth Gamble
NMNH
Smithsonian Institution

Hi Scott,

Thanks for commiserating ;-).

Can you tell me if these are the only key values you include or do you mean those are the headings and you import all that are below those? 

Scott Williams wrote:

I believe the keys were:
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI

I'm trying to figure out the true minimum registry entries that I need to make it work, really don't like putting more in the registry than is really needed.  Also, when I am trying to insert all the module values under the HKEY_CURRENT_USER setting I first have to edit the file to put the current path to the particular user's Reports directory.  Do you do that?

I'm wondering if just inserting the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI setting for the Microsoft Text Driver (*.txt; *.csv), and confirming the odbcjt32.dll is in the system32 dir is enough. I just had to deal with this on an older XP machine and only thought of trying this after the fact, have to wait for next occurrence to test my theory.

Beth :-)

Hi group, 
I'm hoping one of you have experienced this issue at your museum and possibly solved the problem.  On occasion I have users who install EMu but then on first use they get errors relating to the creation / access to the User DSN entries that are supposed to be created for each module to support the ODBC connections needed for Crystal Reports and other reports.  I have not been able to decipher the commonality in order to fix it.  Previously I could reinstall MDAC and get it to work but with newer OSes that doesn't work anymore.  Now I have to manually go in and create them in the Windows Registry.  This has happened on Windows 7 machines as well as Windows XP machines.  As a piece of information that may be a factor; not all our users are Administrators on their machines.  Installs are done by someone who is an Administrator.

The error that is received by the user at login is:

Cannot install User DSN for EMu <module name>.
Component not found in the registry

They will receive numerous version of this for each module and then once they get past that EMu functions OK, minus reporting.  They will continue to get these errors upon every login to EMu.  Very frustrating for users.

Any assistance would be appreciated.

Thanks,
Beth Gamble :-)
NMNH

Hi All,

Beth Gamble here from the Smithsonian's National Museum of Natural History.  Prior to our migration of our Transaction Management functions to EMu party addresses were not really utilized.  For the purpose of handling the important "point in time" address information for transactions during the migration we made several customizations to both the Parties module and the merged new Transactions module (combination of Accession Lots and Loans and Deaccession/Disposal data from Catalog module).  I'm not sure how important it is in general to keep history of addresses over time.  It is however important to keep point in time information about involved parties and their contact info for transactions.  So we keep that information in that module and allow the current information to be stored in the Parties module.  In the Parties module for Person type records we created a new tab called Affiliations which allows for a history of organizational affiliations of an individual over time.  We do find that information very useful in a general sense.  This also created a recursive link back to the parties module to record the organization the person is/was associated with.  The multi-valued grid on the Associations tab contains the following fields:

Organization - link to an Organizational Party record)
Current?  Yes/No to mark which of the affiliations is current.
Position - text file for the position or title held at that organization
Start Date - when they began
End Date - when they left
Comment - optional text for any additional details.

When a Current Affiliation is created for a Person record the system asks if the user wishes to retrieve the address information from the organization record and copy it to the Person record.    The address can be tweaked for person specific address details like route codes or room numbers and such if desired.

In the Transactions module we have two link fields in a multi-valued grid for the transactors.  The first field is the Contact and will be a link to a Person or Position party record.  The second is an Organization field which is a link to an Organization party record.  The Transaction also has copy address fields in this grid.  When a new transaction is created a user usually selects a particular contact record from the Parties module, upon insertion the current organization affiliation for that person is copied into the organization link field on the transaction and the postal address or shipping address (can be selected on the transaction screen) is copied into the corresponding fields in the transaction record.  Address fields are completely read-only in the Transaction Module.  While the transaction is being processed (Status field is other than CLOSED) the copy address fields are automatically updated with changed made to these fields in the corresponding linked party record.  Once CLOSED those copy fields become static and are no longer updated with changes in the linked Party record.  This maintains our point in time data.  The same functionality was added to our Movement module which we renamed Shipments.

The one issue that isn't covered in this implementation is change of person names (marriage etc.) and Organizational name changes.  For these I think we would create new records.  Associate the records to the old name records and change the record status of the old names to Inactive so they don't appear in default queries.  By doing this it would insure that the names in past transactions would be preserved as they were at the time of the transaction.

We have a huge data clean up / merge of records to do in our parties module as a result of the migration of our old TM system's data.  There was pretty much no way around that.  We too are finding this task very difficult to do in bulk.

I hope that makes sense to folks.  So far we are happy with how this is working.

Beth Gamble
SI - NMNH - Informatics Office

Hello, I know this is a very old post and you probably have solved the problem by now but if not I have found that this works only if you make the Datamax printer the default printer on the PC you create the label report on and the one you print from.  It is annoying but I think it works.

Speaking for SI's NMNH, we want to see this change implemented in the next client. Ian is being kind but this was actually an oversight we (NMNH) made in documenting the original Lat/Long Precision changes. It was something we didn’t think of until the change was made and the users saw the data with the extra precision in the centroid calculations for single point values.

Our Apologies,
Beth :-)

--- Beth L. Gamble ----------------------------------
Senior Systems Analyst
National Museum of Natural History
Smithsonian Institution
PO Box 37012 - MRC 136
Washington, DC 20013-7012
p: 202-633-0851
f: 202-633-9562
e: gambleb@si.edu
--------------------------------------------------------------
Life is too short for drama & petty things,
so laugh hard, love truly and forgive quickly

Hello All,

I promised to post my presentation from the 2008 NA EMu Users Meeting regarding creating duplicate label reports using the texxmlreplicate backend utility. Here it is. I did correct the screen shots in this version to reference the same report in all instances. I had mixed two reports screen shots in the version I presented. If you have any questions about using this at your institution, don't hesitate to contact me.

Cheers,
Beth :-)

PS - I hope the ppt file gets attached correctly.

Attachment: BLG-Texxmlreplicate-EMu-conf-2008-fixed-screen-cap.ppt

-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

31-Oct-07 11:00:00
Category: Using EMu

Hi Mark,

If there is only ever one Artist Role Creator in the nested table for a catalog record then the way to do this is to actually also link the Creator table(s) to the main report. Use the Select Expert to only retrieve the "Artist" role value from the table. Then sort on the link creator name field. As long as this is a one-to-one relationship you can do it this way. Then you don't need the Artist subreport anymore but you will need the subreports for the other creator roles. If there can be multiple Artists per catalog record then the catalog records will be duplicated in the main report for as many artists there are associated with it. Since I work at a Natural History museum we don't have a creator nested table like yours so I can give you exact screen shots of what I'm talking about, sorry. Here is an example of where I have done this in Crystal with the Other Numbers nested table looking only for Field Number:

Here is what my main report's database expert links tab looks like:
https://emu.axiell.com/images/agorapro/attachments/63/mini_select-expert.JPG
https://emu.axiell.com/images/agorapro/attachments/63/mini_database-expert.JPG


In this report I was then able to sort on CatOtherNumbersValue to sort on Field Numbers. Obviously yours will be a bit more complicated because your creator table then links to Parties to get the name fields but as long as you select only by the role "Artist" you should be good to go.

Hope this helps,
Beth :-)

-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

Hi All,

I posted the following in the Sites Forum when the email was not working. I just wanted to bring this to folks attention. Please see the full post at EMuUsers.org to see the attachment.

Thanks,
Beth :-)

Hello EMu Users,

NMNH has been requesting / begging KE to increase the precision at which they are calculating the decimal degree value from an entered DMS latitude or longitude value for a very long time. It was requested by KE for us to get a larger body of approval for this change in conversion philosophy. We finally did this at the October 2006 North America EMu Users Group meeting. The group we presented this to and obtained approval from was the Natural History EMu users group.

I then dropped the ball on this and failed to get a summary of those changes to the group. I have rectified that today and also wanted the larger EMu community as a whole to see as well. Hence my submission here.

If you have any questions or comments please don't hesitate to contact me.

Cheers,
Beth :-)

Attachment: Lat-Long-DMS-to-Decimal-conversion.pdf

-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

I have gotten this to work by doing the following:

Create a formula to be placed in the group header (assuming your report is grouped by Herbaria and you want it to reset at the start of each herbaria). This formula just defines and sets value of shared variable to current balance in db.

Ex: Shared NumberVar sn_exchangebalance := ;

The second formula would be in the detail section:

WhilePrintingRecords;
Shared NumberVar sn_exchangebalance;

if (not IsNull({emovemen_csv.DatScheduledMovementDate})) then
sn_exchangebalance := sn_exchangebalance + Truncate(CDbl ({emovemen_csv.ObjNumberOfObjects}))
else if (not IsNull({emovemen_csv.DatArrivalDate})) then
sn_exchangebalance := sn_exchangebalance - Truncate(CDbl ({emovemen_csv.ObjNumberOfObjects}));

sn_exchangebalance;


The WhilePrintingRecords is important in getting this to work properly. Not having it may be why your previous attempt was not working.

Hope this helps.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

Hello,

The National Museum of Natural History will be embarking shortly on their migration from their existing Transaction Management application to EMu. One of the biggest dilemmas we need to address is the recording and maintaining of point in time type of data for the transactions. The transactor's (donor, lender, borrower, etc.) specifics must be maintained as it appeared at the time of the transaction. However, if this is done via linking to party module records, how is the best way to maintain that history, and allow it to be fairly easily reported on? For folks who have implemented their transaction module(s) in EMu can you speak to how you are addressing this issue, if you are? I'm wondering if others aren't that concerned with keeping the history information of their transactions intact.

There are a few ways I have thought about to deal with this. When actual updates are needed to party records (not just typo or minor aesthetic adjustments) a new record is created and the old record is retired. This is probably the easiest way to handle the problem but puts the burden on the user's to manage their parties module this way. Another way would be to use the party module as picklist at data entry but data would be copied into fields within the transaction module itself. A link would not be maintained. There are issues with both of these methods. I'm just curious if you have come up with other solutions or have other ideas you would like to share.

Thanks in advance for any insights.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

09-Nov-05 11:00:00
Category: Using EMu

Hi Philip,

I have actually used both of the Excel export formats; MS Excel 97-2000 and MS Excel 97-2000 (data only). I have also used Tab-seperated text and Seperated Value (CSV) formats depending on the need. I use these exports only when I am creating a report specifically for the purpose of export of data (flat file). Therefore the report isn't pretty by any means and any of these formats output in a similar way. In order to have any of the exports work without inserting blank columns or rows you have to bump all fields/sub reports up to the very top of the section and size the fields so they are right up against each other. Size all the fields the same height and then bump the bottom of the section right up against the bottom edge of the fields. For Subreports make sure the fields in the subreport also are formatted this way and the field or fields in the subreport take up the entire subreport width. This part of the design is very much tedious trial and error. This method isn't perfect but it does work. I like to think of it as the MacGyver technique ;-). I hope this answers your question.

Beth :-)
National Museum of Natural History - Smithsonian Institution
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Matt,

Glad to have been of help. When you want to solve the formatting into one long string issue check out my previous post in the EMu-l Archive Forum as mentioned earlier. It really does work ;-).

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Remove ColColl_csv completely from your main report.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Actually Matt I think your subreport link is a bit off. ecatalogue_key field from the main report should come from your main catalog data table which is usually ecatalog_csv. ColColle_csv should no longer be in your list of tables in the main report. ecatalog_csv.ecatalogue_key from main report should link to ColColle_csv.ecatalogue_key in the subreport.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Matt,

I think your link in the sub-report is correct. I think the problem may be that you still have the ColColle_csv table linked in your main report. Since it is now in your subreport you do not want it linked in your main report. Remove ColColle_csv from the tables in your main report.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Hi Matt,

Not sure if you have found my previous post in the EMu-l Archive forum yet but in it I describe using the WhilePrintingRecords feature to assist in the printing of just one line for multiple records in the sub-report. Also, there is a technique described there for using the conditional formatting capabiltiy to supress sections of the report based on which record you are processing, which might be of use. I highly recommend you stop avoiding sub-reports though. They are a necessary component of reporting and very powerful tools. Yes their processing adds time to the report generation but they are so versatile that it makes up for it.

If you really want to avoid sub-reports you can also utilize groupings in the main report to remove duplicate rows. However, once your report has more than one one-to-many relationship fields that you want to collapse down to one record you will have to use sub-reports.

I have found a way in Crystal to do everything I have wanted to do so far in reporting. Yes, some of the techniques are a bit convoluted, not nearly as neat as programming in java or perl or such. But it can be done.

Hope I have been of help.

Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

15-Oct-05 09:00:00
Category: Using EMu

Hello,

I echo everything Ian said and detailed so well. Any one-to-many relationships in your data (show as a multi-value field or in a grid in EMu) will result in multiple lines in your report unless you break them out into seperate sub-reports or do groupings in your main report.

I noticed in the formula you created you are attempting to get the collector names in a string with commas seperating the names. A basic sub-report will not accomplish this for you. It will just put the collectors on individual lines of the sub-report. Basically looking like the following for a record with 3 collectors:

John Doe Collector
Jane Doe Collector
Fred Collector

The method that I was taught by a KE staffer for collapsing this into one string is described in a previous post to the old EMu list. It can be found in the EMu-l Archive forum, thread title "Multiple Creators in Excel Reports" posted 12/10/2004. If you can't find that post or have trouble deciphering it let me know and I'll repost.

Once you learn this technique you will be using it all the time. I know we do.

Happy Reporting,
Beth :-)
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

Hello EMu Users,

During the fantastic North American EMu User's Group meeting in Chicago I learned, from our beloved KE developer Bern Marshall, how to search for punctuation/special characters in an EMu Query. Please be aware that this is for power users of EMu to use, I wouldn't recommend making it known to your entire user base.

Here is how to do it -

1. Enter into the field you want to search for a special character any letter followed by the character. For instance type a+ if you wish to search for a plus sign. Or a? if you wish to search for a question mark. The character is needed to force the creation of the query expression. Add any other query terms to other fields.

2. Select the Show Search... menu item from the File menu.

3. Locate the particular part of the resulting TexQL statement where the special character parameter is specified.
For example: CitTypeStatus contains 'a-'
Replace the word contains with the word like, remove the bogus letter you used to create the search and put *s around the special character so it finds the character anywhere in the text of that field.
Result: CitTypeStatus like '*-*'

3a. Special note - If you are searching on a character that has special meaning to texpress such as * ? ( ) etc. You must escape the character so the query treats it like a character instead of it's special meaning. The escape character is a backslash \.
Result: CitType Status like '*\?*'

4. Click the OK button to begin the modified search. This type of search does not use the index so it will be slow to return results but it does work.

I hope this is useful to you all. If this isn't clear or you have follow up questions please feel free to contact me but perhaps Bern might be a better contact (Sorry Bern!!).

Yours truly,
Beth Gamble (formerly Beth Strohmayer :-))
National Museum of Natural History
Smithsonian Institution

PS - Great to see so many of you in Chicago. I'm very much looking forward to a flurry of activity on EMuUsers.Org. Thanks so much Forbes for creating this online arena for us.
-- Beth L. Gamble - Senior Systems Analyst
Informatics Office,
Office of the Assistant Director for Information Technology
National Museum of Natural History
Smithsonian Institution

11-Dec-04 11:00:00
Category: Archive
Forum: Archive

Hi All,

A few extra notes on ths technique. Crystal's export to Excel can be very
very slow and also seems to bomb on exports of large record sets. So if you
are exporting a large set of records (say over 2500) you may need to run
the report and export several times on subsets of the record set and then
merge them after export. As I said, this is not an ideal solution but a
geeky kludge to at least get something.

Lee-Anne, multiple tricky things in the same report is something we do all
the time. Basically each multiple links field trick is a different
subreport linked to the master report. The first taxon name trick would be
the suppressing the details section formula I mention toward the end of my
post. The collector and identifier tricks are the main technique I
described and each would be in their own subreport. This may be overkill to
mention this but if a particular CSV file is used in the subreport it does
not and should not be included in the main report. This is very important
to avoid the duplication of your main report data fields. My rule of thumb
is if it is a one to one relationship it goes in the main report. One to
many relationships go in subreports or you must create appropriate groups in
the main report to avoid duplication.

Many of our reports turn out to be only a few key catalog fields and a boat
load of subreports. This can make the report processing slow but it seems
to be the only way so slow is better than nothing in the grand scheme of
things.

Happy Holidays everyone,
Beth :-)

10-Dec-04 11:00:00
Category: Archive
Forum: Archive

Hi Will and others,

Here at the Smithsonian Institution's National Museum of Natural History,
we have gotten around this issue by using a Crystal Report solution then
exporting from Crystal to Excel. Within Crystal the field or fields that are
in grids are combined together using a subreport. The subreport contains
three formulas. Here is an example for combining multiple collector names
into a single string of collectors. (Could easily substitute creator instead
of collector)

First formula defines and initializes a Shared StringVar variable to a
blank string. This first formula is placed in the suppressed report header
section.

Shared StringVar ss_collectors := "";

Second formula is the processing formula to combine the fields and rows of
the grid into one long string. The long string in this examble is formated
as follows: Collector: With:
name>, .... and .

WhilePrintingRecords;
Shared StringVar ss_collectors;
If ss_collectors = '' Then
ss_collectors := "Collector: " + {Collecto_csv.NamFullName}
Else
If InStr (gs_collectors, "With:") = 0 Then
ss_collectors := ss_collectors + " With: " +
{Collecto_csv.NamFullName}
Else If NextIsNull ({Collecto_csv.NamFullName}) Then
ss_collectors := ss_collectors + " and " +
{Collecto_csv.NamFullName}
Else
ss_collectors := ss_collectors + ", " +
{Collecto_csv.NamFullName};

This formula is placed in the Detail section. The WhilePrintingRecords
processing function is important so don't forget to include it. The Details
section is also suppressed. This may seem weird but what we are doing is
using the detail section for processing only. This will then allow us to
just have one row of data generated for what normally would be multiple
rows.

Last formula is simply the formula that prints out our nice long string
shared variable. This is placed in the unsuppressed report footer field.
WhilePrintingRecords;
Shared StringVar ss_collectors;
ss_collectors;

Again, the WhilePrintingRecords is important here so don't forget to
include it.

Now the tricky part is how to get this all lined up properly in Crystal so
when it is exported to Excel there are no blank columns or rows in the
output. This part is time consuming and involves a lot of trial and error
but is not impossible. Using the alignment and sizing tools in Crystal you
can assure that alll of your fields and subreports are the same height and
top aligned to each other and the top of the section. The other trick is to
bump each field and subreport right up against the one before and after it,
leaving no white space between fields. For fields in subreports, make sure
the printing field is at the top left most position of the section it is in
and is as long as the subreport field length. In other words have it take
up the entire width of the subreport size.

One other trick I use if I only want the first row of a multi row grid to
print is to create a subreport, put the fields desired in the detail section
and in the detail section's suppression formula I put the following
command:

Not OnFirstRecord;

This evaluates to True for all records except the first one meaning the
detail section will be suppressed for every record except the first. Only
the first record's data is printed.

I hope I have done an adequate job of explaining this technique. It isn't
ideal but it does work. If you have any further questions don't hesitate to
ask.

Beth :-)

Informatics Office,
Office of the Assistant Director
for Information Technology
National Museum of Natural History
Smithsonian Institution

  • Index
  • » Users
  • » gambleb
  • » Profile

Board Info