Hi Mark,Thanks for the quick reply. I must have confused the community with another forum :-P
Hi Erwin,Thanks for pointing to this workaround.It has striking similarity to my own workaround,It turns out that having SQLServer Management Studio installed is required for a working report.…CR reports stopped working on client machines that do not have SQL Management Studio installed with the difference that they use Management Studio 2012 😜I still could try whether such an old version of MSSMS induces the correct changes in a client system. That would prove that it is not a case of a newish addition that breaks the reports. Even so: installing the management studio on each users’ system would be inconvenient.
Hi Jasper,Thanks for chiming in.We had a look at the TLS version, but their server is older than that so it should not be a problem.@Erwin Ekkel , upon re-reading your comment, I realize I misread it on first sight. I read `native client` as `Microsofts own SQL Server client`, ie, the management studio. I now realize it is a driver package of sorts.I'll contact my customer and post back after they have tested this. Thanks both of you!
> we have incorporated various new Description fieldsWohoo, great! > If you do identify specific screens where this improvement is crucial, please feel free> to create a separate, more detailed idea for our consideration.Thanks :-)
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.