Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Number too large for crystal

Status
Not open for further replies.

APB1981

Technical User
Jul 10, 2005
83
NO
Hello I have a very complex problem I need help with.
I need to sort the order of transactions in my database but many transactions have the exact same transaction date. There is also a unique timestamp field but I can not use this alone as a user can specifiy the transaction date manually and timestamp number will always be based on today. I want to join these 2 fields together somehow and group the material that way. The only problem is this generates a number too large for crystal: 2.01e+026
yyyymmddhhmmss&1234567891
and the summaries can not pick up the correct miniumum date and maximum date.

Any ideas.

Crystal R2
MSSQL 2005

Thanks

APB
 
How are you joining, your same number is not that big. Looks like your concatenation process is doing something wrong.

Please show formula with sample data before you concatenate.

Ian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top