Search results for query: *

Have you looked at Control Panel|Regional Settings |Number formatting properties of the PC?

What you say seems reasonable. However, everything else about the report still works - just the parameters(0,1). I can see that I will have to recompile the whole VB source with VB6 and CR7 references/components. Thanks.

I have old reports compiled with CR6. The VB.exe passes parameters using .ParameterFields(0), .ParameterFields(1) These parameters are passed by CRPE to SQL Stored Procedures and the report works. I now need to edit the report, add some more fields that kind of thing ... but with CR7. And now...

Thanks for this ... I had trawled thru all of the TechNet/Knowlegde Base stuff but I need to export in a variety of formats (typical) and RTF was causing real problems. Sounds like CRPE DLL not handling the format to RTF properly? Any idea how to reduce the dropdown list of formats to say just...

There are many ways but so as to avoid any 'formatting' interference by various system's settings ... Probably best to pass as a string. In Crystal Reports: Insert|Formula New Name it VBDateTime Put a default in such as "01/01/1980 12:00:00" Then you know wheteher your passing has...

I have a 'spreadsheet' lokking result of a Crystal Report. Exporting as e.g. Excel 7.0 gives a reasonable result but when exporting as RTF ... all of the right justified columns (common when dealing with figures) come out as a complete mess! Any ideas?

... need to know what the formula '@char' is? in order to help you further. i could show you some examples but they would be more meaningful if you state what @char =

... This works quite well but it doesn't update the where clause when you go to Show SQL Query. In some cases I have noticed the report runs very fast and in others it takes a long time. I assume it is pulling all records and then executing the record selection formula when it takes a long...

Yes I think a good tip for fixing v7.0 problems IS to get v8.0. I am going to be quite interested in the SCR that'll come with Visual Studio.net though.

Steve! Thanks for your (detailed) attention on this. Now. Guess what? I have learned of a MR1 patch today. And guess what? It looks like this is going to fix things! It seems the entire Parameter Insert process is completely different from what has been distributed over the network to the users...

Thank you all for your attention to this matter. I can agree with Steven's synopsis on first hearing about the problem - most problems of this nature are indeed all of the things listed - BUT just take a simple step back for a moment - the issue IS that the parameter field (OK so there may be...

Thanks for having a look at this; however Create a report to simply list all the records of a table in SQL Server which has a date field. (My table has 230,000 records). Then Insert|Parameters to accept a @StartDate and an @EndDate. Run the report. Yes, you will get the results back that you...

I need to allow the user to enter e.g. Start Date and End Date to filter on a large table. Setting up the parameters seems no problem, and Database|Show Query seems to require entry of these parameters before in fact showing the query - but then no WHERE clause with the parameters i.e. SQL...