125
Hi, we are running Solomon 6.0 and whenever I try to run a report, I get this error.
SQL Server Message 10039
Attempt to convert data stopped by syntax error in source field
Debugging info: MS_strtotime - dbconvert
Optional info: 07435400
Anyone know what this means?
*This post is locked for comments
Dear vincent28,
following your experience, I have just solved my problem. :)
thanks you very much!
thanks for reply. I will reinstall and inform to you the result. :)
Hi,
Yes, I spent a lot of time trying to find the solution but nothing was found. So I basically reinstalled windows on that machine, and start everyting from scratch and this fixed the problem. I understand that formatting and reinstalling is the least preferred method, but sometimes, you just have to do it.
Hope this helps.
V.
Dear vincent28,
I have problem like you, but I can not solve it. did you solve your problem? pls tell me how to solve it.
thanks & best regards
Hi Gail, thanks for replying. To start with, I am not familiar with Solomon but since the Solomon expert in our company is on vacation, I am just trying to help and I will provide as much info as I can.
I don't believe I saw any Crystal error. The error mentioned above is the first error that came up whenever I try to run any reports, only form this computer. The report is a customized report, but as to how the customization works, I am not sure. Since this only happens on one computer, there must be something that is running abnormally on this machine. So if I cannot find a solution anytime soon, I will try to replace this user's computer and see what happens.
Thank you for your time.
Are you getting a Crystal error prior to getting the SQL error? If so, what is the Crystal error number and what does it say?
Are you running a template that contains a select statement, or are you simply running a select statement? Is the select statement pointing to a date or time field? If so, could you provide the value you're using to select on the date or time field? Are you using "between" in the selection? [We used to have problems in V6.X with date syntax on select statements that generated errors like this.]
Is this an error you only get on one workstation when you run it or do all users get the error on this report regardless of the workstation? Do you get this error on every report run on this workstation or just the one report?
Is the report a generic report or has it been customized? If standard, what is the report number? If it has been customized, are there custom fields that are date/time related?
This kind of info would help us to identify where to look to solve your problem.
Best regards,
Gail J-N
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,399
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
