Hello,
I already sent my problem. But, i didn't get any solution. So, i am sending it again.
I want to print a report in multiple printers in networking. How is it possible through VB6.0?
Please help me.
Regards,
RajasekharYou should be able to make a cycle for each printer you have,
and then print the report to that printer...
If using default, you could set in the cycle each printer as default
and print, then step to next printer...
Showing posts with label sending. Show all posts
Showing posts with label sending. Show all posts
Sunday, March 11, 2012
Tuesday, February 14, 2012
Cross database manipulation
Hi everyone!
I recently found out that using ADO to connect to the SQL server without mentionning the data source; then, by sending a query with the following syntax: dbname.owner.tablename.columnname... an implicit connection to the data source (database) is performed automatically. This way of connecting allowed me to manipulate accross two or more databases thing that is necessary in my project.
My question is:
1- Do anyone have any bad experience and/or negative consequence to such connectivity (memory consumption, unexpected disconnection, ...)? Please consider a very high frequency of manipulation since we are dealing here with a 24/24 hour operational site.
2- Are there any alternative solutions for cross database manipulation (select, insert, update, delete)?
ThanksGot Code?
Personally I don't believe it...
I googled this...
http://www.able-consulting.com/ADO_Conn.htm|||I've found using three part names to work lovely on databases on the same server, and ]url=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_qd_12_5vvp.asp]four part names[/url] work for databases on other servers (assuming that permissions are Ok).
These are 100% supported, and a nice, clean way to get access to remote data.
-PatP
I recently found out that using ADO to connect to the SQL server without mentionning the data source; then, by sending a query with the following syntax: dbname.owner.tablename.columnname... an implicit connection to the data source (database) is performed automatically. This way of connecting allowed me to manipulate accross two or more databases thing that is necessary in my project.
My question is:
1- Do anyone have any bad experience and/or negative consequence to such connectivity (memory consumption, unexpected disconnection, ...)? Please consider a very high frequency of manipulation since we are dealing here with a 24/24 hour operational site.
2- Are there any alternative solutions for cross database manipulation (select, insert, update, delete)?
ThanksGot Code?
Personally I don't believe it...
I googled this...
http://www.able-consulting.com/ADO_Conn.htm|||I've found using three part names to work lovely on databases on the same server, and ]url=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_qd_12_5vvp.asp]four part names[/url] work for databases on other servers (assuming that permissions are Ok).
These are 100% supported, and a nice, clean way to get access to remote data.
-PatP
Subscribe to:
Posts (Atom)