hello
How i run vb application using a crystal report on any other machine on which crytsal report isn ot installed ?
how can we embedd crystal report in visual basic to make trake ur reports.. ?
Is it possible that we make a crystal report in Crystal report and direct call it on the setup time when other computer not contain crystal report..?
What is the run Time dll required for crystal Report in our application....???
please help me .. if some one know about the process , please alos let me know... thank you
ankur bhatnagarIf you have referenced the crytal reports in your project, then just make a setup of the project and install it in other systems that do not have crystal reports.
The setup will take care of installing the DLLs and OCXs required for crytal reports to run on the system.
Crystl32.OCX is the OCX file for the crystal report control
crviewer.dll is the dll for crystal viewer
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
Crystal REport run time error 6 over flow
In win98 se..i get run time error 6 over flow..when i try to open crystal report through a vb application on the client machine...i try to isolate the problem..what i found is that while displaying images..there is no problem..integers no problem but when data in string format (for example product name) is put onto the report..it prompts this error...the applicaiton works fine on xp..i dont know how to fix this problem..could any one please help meCheck if there are any viruses on that system
What does that string look like?
Does it have special characters?
What does that string look like?
Does it have special characters?
Sunday, March 11, 2012
Crystal Report Indexing
My report is calculating the sum of spindles in spindle table for number of machines. Each machine contain 480 or above spindles.
When I calculate to total bags produced by number of machines during the month, it calculte wrong and shows very huge amount like 72480 instead of 142 or something else.
When I remove the field which calculate the total spindles then it shows correct sum of total bags.
I want to know what is the problem. Or what is the indexing scheme.
I have checked normalization and mapping of database tables both in crystal report and SQL Server 2000. These are correct.
ThankyouCan you post some sample data and the result you want
When I calculate to total bags produced by number of machines during the month, it calculte wrong and shows very huge amount like 72480 instead of 142 or something else.
When I remove the field which calculate the total spindles then it shows correct sum of total bags.
I want to know what is the problem. Or what is the indexing scheme.
I have checked normalization and mapping of database tables both in crystal report and SQL Server 2000. These are correct.
ThankyouCan you post some sample data and the result you want
Thursday, March 8, 2012
Crystal Report Developer Runtime
In my VB application I can print some reports. From my pc all works right but if I do it on a machine in which CR10 is not installed I get errors.
What Dll's are needed to run CR?
I've searched on the web, but I haven't found a solution.
I think I must create an installer package with all dll's but how could I do this?Dunno about V10, but in 8.5 installation, there is a file named Runtime.hlp that is found in
C:\Program Files\Seagate Software\Crystal Reports\Developer Files\Help
this tells you what the files are that are needed for particular deployments.
Under Vb6's Add-Ins menu item there should be a Package and Deployment Wizard option. This will use the dependency files (.dep) that ship with Crystal to build up a complete set of files and define the locations they are to be installed to etc. These .dep files contain information about files that are needed in order for specific functionality to occur, and whether windows needs to register them or not, and so on. Do a search for cr*.dep on your development PC and have a look inside these files, you'll see what I mean.
Sometimes you have to tweak the installation, as the .dep files are not up to date or are incorrect, and it's best, if you run into problems, to check Seagate's Business Objects site for assistance.
Bear in mind, in this Runtime.hlp they reference file locations that refer to the location of files on your development PC. They don't list where the files have to go on the PC with the deployed VB application........you gotta rely on the .dep files being OK, and then working any other bugs out for yourself.
dave|||Ok, thank you very much!
Grazie, ciao :-)
What Dll's are needed to run CR?
I've searched on the web, but I haven't found a solution.
I think I must create an installer package with all dll's but how could I do this?Dunno about V10, but in 8.5 installation, there is a file named Runtime.hlp that is found in
C:\Program Files\Seagate Software\Crystal Reports\Developer Files\Help
this tells you what the files are that are needed for particular deployments.
Under Vb6's Add-Ins menu item there should be a Package and Deployment Wizard option. This will use the dependency files (.dep) that ship with Crystal to build up a complete set of files and define the locations they are to be installed to etc. These .dep files contain information about files that are needed in order for specific functionality to occur, and whether windows needs to register them or not, and so on. Do a search for cr*.dep on your development PC and have a look inside these files, you'll see what I mean.
Sometimes you have to tweak the installation, as the .dep files are not up to date or are incorrect, and it's best, if you run into problems, to check Seagate's Business Objects site for assistance.
Bear in mind, in this Runtime.hlp they reference file locations that refer to the location of files on your development PC. They don't list where the files have to go on the PC with the deployed VB application........you gotta rely on the .dep files being OK, and then working any other bugs out for yourself.
dave|||Ok, thank you very much!
Grazie, ciao :-)
Saturday, February 25, 2012
CryptoAPI function 'CryptAcquireContext' failed
Hi,
I am receiving the following error after installing MSDE
on a machine with NT 4.0 SP6a:
MSSQL Server logon. Connection failed. SQL State 42000 SQL
Server error 552
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI
function 'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize
correctly.
I have found the following KB article which addresses
this, but don't know how to sign on to the server using
sysadmin login.
http://support.microsoft.com/default.aspx?scid=%
2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D32 1459
If anyone has seen this before would be very interested to
hear.
Many thanks,
Mark.
Yep... I've had this problem - or rather a customer 4000 miles away did.
As we were unwilling to advise the customer to do the fix - as we'd be the
ones responsible for 'trashing the machine' if it went wrong, we gave the
customer a link to the article. They didn't fancy doing it, their IT
looked at it and did not want to do the BOOT.INI thing either.
They upgraded subsequently to Win2K, bringing forward that users upgrade
window.
I am receiving the following error after installing MSDE
on a machine with NT 4.0 SP6a:
MSSQL Server logon. Connection failed. SQL State 42000 SQL
Server error 552
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI
function 'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize
correctly.
I have found the following KB article which addresses
this, but don't know how to sign on to the server using
sysadmin login.
http://support.microsoft.com/default.aspx?scid=%
2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D32 1459
If anyone has seen this before would be very interested to
hear.
Many thanks,
Mark.
Yep... I've had this problem - or rather a customer 4000 miles away did.
As we were unwilling to advise the customer to do the fix - as we'd be the
ones responsible for 'trashing the machine' if it went wrong, we gave the
customer a link to the article. They didn't fancy doing it, their IT
looked at it and did not want to do the BOOT.INI thing either.
They upgraded subsequently to Win2K, bringing forward that users upgrade
window.
cryptoAPI
When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
cryptoAPI
When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
> http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
> > When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with
our
> > VB6 application we sometimes get this error
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> > 'CryptAcquireContext' failed.
> > Error 0x8009001d: Provider DLL failed to initialize correctly.
> >
> > On Win2000/2003 XP we not get this error any one come across this before
> >
> >
> > Thanks
> > Andy
> >
> >
> >
>
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
> http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
> > When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with
our
> > VB6 application we sometimes get this error
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> > 'CryptAcquireContext' failed.
> > Error 0x8009001d: Provider DLL failed to initialize correctly.
> >
> > On Win2000/2003 XP we not get this error any one come across this before
> >
> >
> > Thanks
> > Andy
> >
> >
> >
>
cryptoAPI
When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
cryptoAPI
When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI functio
n
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/defaul...kb;en-us;321459
http://support.microsoft.com/defaul...kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI funct
ion
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/defaul...kb;en-us;321459
> http://support.microsoft.com/defaul...kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our[vbcol=seagreen]
>
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI functio
n
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/defaul...kb;en-us;321459
http://support.microsoft.com/defaul...kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI funct
ion
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/defaul...kb;en-us;321459
> http://support.microsoft.com/defaul...kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our[vbcol=seagreen]
>
cryptoAPI
When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
VB6 application we sometimes get this error
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/defaul...kb;en-us;321459
http://support.microsoft.com/defaul...kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/defaul...kb;en-us;321459
> http://support.microsoft.com/defaul...kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
> > When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with
our
> > VB6 application we sometimes get this error
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> > 'CryptAcquireContext' failed.
> > Error 0x8009001d: Provider DLL failed to initialize correctly.
> > On Win2000/2003 XP we not get this error any one come across this before
> > Thanks
> > Andy
Friday, February 24, 2012
Crossjoining data from 2 datasets
Hi,
I have one dataset DS1 connected to one SQL 2005 server DB, another dataset DS2 to different server on different physical machine, different SQL 2005 DB. I'm trying to build only one chart which data is based on those two different datasets DS1 and DS2. I understand that I can use subreports to use two different datasets, but how can I crossjoin those data together in one chart?
Thanks!
You need to combine the two datasets already in the dataset query. Some options to consider:
? Linked Server functionality (see http://msdn2.microsoft.com/en-us/library/aa213283(SQL.80).aspx)
? OpenRowSet functionality to join data from another database server into the current query (http://msdn2.microsoft.com/en-us/library/ms190312.aspx, http://msdn2.microsoft.com/en-us/library/aa276850(SQL.80).aspx)
-- Robert
|||
Thanks a lot Robert!
Linked server helped a lot!
Crossjoining data from 2 datasets
Hi,
I have one dataset DS1 connected to one SQL 2005 server DB, another dataset DS2 to different server on different physical machine, different SQL 2005 DB. I'm trying to build only one chart which data is based on those two different datasets DS1 and DS2. I understand that I can use subreports to use two different datasets, but how can I crossjoin those data together in one chart?
Thanks!
You need to combine the two datasets already in the dataset query. Some options to consider:
? Linked Server functionality (see http://msdn2.microsoft.com/en-us/library/aa213283(SQL.80).aspx)
? OpenRowSet functionality to join data from another database server into the current query (http://msdn2.microsoft.com/en-us/library/ms190312.aspx, http://msdn2.microsoft.com/en-us/library/aa276850(SQL.80).aspx)
-- Robert
|||Thanks a lot Robert!
Linked server helped a lot!
Subscribe to:
Posts (Atom)