| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Asynchronous vs Synchronous
--0-1681692777-964102508=:17351
Content-Type: text/plain; charset=us-ascii
Actually some older versions (7.3.x?) of sqlnet didn't support async cancellation of a query. Later versions do. We use several of Quest's tools (toad, sql navigator, and sqlab xpert) and they all let you cancel a query immediately by pressing a cancel button. "Wasserman, Sara" <sjwasserman_at_pscnet.com> wrote: We use Cognos Impromptu to do ad-hoc database queries. An Impromptu user can cancel a query on the database from Impromptu. Impromptu uses SQL*net to communicate with the Oracle database. I don't know anything about asyncronous vs. synchronous, but it does sound like Seagate is trying to blame Oracle for Crystal Report's own shortcomings. A SQL*Plus or SQLWorksheet user can also cancel a query from a client.
Maybe you should investigate other query tools for one that will allow your users to cancel queries.
Sara
> -----Original Message-----
> From: Christine Turner [SMTP:Christine.Turner_at_IPS-Sendero.com]
> Sent: Wednesday, July 19, 2000 12:00 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Asynchronous vs Synchronous
>
> Hello All,
>
> This is the response I received from my developer that he received from
> Crystal. Anyone have any comments?????
>
> Thanks In Advance,
> Cheers!
> Christine Turner
> Database Administrator
> IPS-Sendero
> Scottsdale, Arizona
> Phone: (800) 321-6899 ext. 3286
> Fax: (480) 946-8224
> E-mail: christine.turner_at_ips-sendero.com
>
>
>
> -----Original Message-----
> From: David Denison [SMTP:david.denison_at_ips-sendero.com]
> Sent: Tuesday, July 18, 2000 3:47 PM
> To: Christine Turner
> Subject: Fw: CTL:20000717-10296 Automated Response:
>
> Here is that Crystal response concerning synchronous vs. asynchronous
> database connections.
>
> ----- Original Message -----
> To:
> Sent: Tuesday, July 18, 2000 1:32 PM
>
>
> > This EMail was sent: 7/18/00 1:32:20 PM (Pacific Standard Time)
> >
> > *** This incident has been closed. To reopen, simply reply to this
> email
> > with the additional information. Do not use this Control Number for a
> > different question as it will go to the wrong support group ***
> >
> >
> --------------------------------------------------------------------------
> > ------------------------------------
> >
> > Response To: David Denison
> >
> > Hi David,
> >
> > Thank you for using Answer by email.
> >
> > Unfortunately what you're trying to do will cause a gpf, and let me
> > explain why.
> >
> > If we submit a query to your database (in this case Oracle), we send off
> a
> > SQL statement (i.e select * from table). Oracle processes that
> statement
> > and generates a dataset and passes that back to Crystal Reports to
> format
> > and display.
> >
> > If we cancel the job or close that preview window before that data comes
> > back there's no way to tell Oracle that we've cancelled that job and
> it's
> > going to continue sending data to memory that Crystal Reports has
> already
> > released back to Windows and it will crash. This bi-directional
> > communication would require an asynchronous database driver on BOTH the
> > Crystal Reports side of the connection and the Oracle side of the
> > connection. Unfortunately, to my knowledge, Oracle doesn't support an
> > asynchronous connection, and Crystal Reports only supports asynchronous
> > connections with a limited number of our database drivers.
> >
> > I've included a Crystal Reports knowledge base article that describes
> > which of our database drivers are asynchronous:
> > c2006041
> >
> > I've also pasted this knowledge base article below:
> >
> > Asynchronous Database Connection Support for Seagate Software
> >
> > Product: Crystal Reports Professional Edition Version: 8.0.0.371
> > Applies to: Reported version and higher
> > Database: Microsoft SQL Server Platform: Windows 95 Date Verified:
> > February 16, 2000
> >
> > Problem:
> > Q: What happens when a user sends off a query in Crystal Reports (CR)
> or
> > in the Info Report Designer in Seagate Info (SI) and then needs to
> cancel
> > that query? How does the processing stop or does it even stop?
> >
> > Q: What is the difference between Synchronous and Asynchronous database
> > connections?
> >
> > Q: Does Seagate Software support Asynchronous database connection?
> >
> >
> > Solution:
> > There are two possible database connection methods with any type of
> > database. They are:
> > . Synchronous Database Connection
> > . Asynchronous Database Connection
> >
> > An asynchronous database connection refers to the ability for a client
> > application to be able to issue any number of commands to a database
> > server at any given point during the database connection, without
> waiting
> > for the database server to complete the processing of current tasks.
> >
> > A primary application of asynchronous database connections, within the
> > Crystal Reports (CR) Designer, is the ability to terminate a running
> query
> > at any point in time.
> >
> >
> > Definitions:
> > =================
> > Synchronous Database Connection:
> >
> > Synchronous connection to a database means that once a SQL query is
> passed
> > to the database server, the calling application (Crystal Reports in this
> > case) waits until it receives a "Finished" message from the database
> > server. The "Finished" message is connected to the first packet of the
> > result set being sent back.
> >
> > In Crystal Reports, if the cancel button is clicked while a synchronous
> > connection is underway, the Report Designer will look as though it has
> > canceled the query request. However, the request on the database server
> > will continue to process until completion. Once the first packet comes
> > back saying "Finished", no more of the query result set will be passed
> > back.
> >
> > NOTE: Actually, when executing the query synchronously, Crystal Reports
> > doesn't get the chance to cancel since the database client won't return
> > control until the database is finished.
> >
> >
> > Asynchronous Database Connection:
> >
> > Asynchronous connection to a database means that multiple sets of
> commands
> > can be passed to the database server and processed at once. (For
> example,
> > there is no need to wait for the query to return before sending another
> > command to the database server).
> >
> > Instead of waiting for a "Finished" message to be sent back from the
> > database server, the calling application (Crystal Reports in this case)
> > sends a query status message to the database server at set times asking
> > "Are you done yet?" When the database server says "Yes", the result
> > packets start coming back. However, if a cancel button is clicked on
> the
> > client computer side, instead of sending a question message to the
> > database server, the client application has the ability to send a
> "Cancel
> > query" message to the database server. In the Crystal Reports scenario,
> > if the cancel button is clicked, instead of asking the database server
> if
> > it has completed its query, Crystal Reports sends a "cancel" message to
> > the database server. The query never has to complete.
> >
> >
> >
> > Database Drivers that support Asynchronous Connections:
> > =====================================================
> > The following CR database drivers include support for asynchronous
> > database connections:
> >
> > . Microsoft SQL Server Direct (P2ssql.dll) - 8.0.0.1 and higher
> > . Sybase Direct (P2ssyb10.dll) - 8.0.0.0 and
> > higher
> > . IBM DB2 Direct (P2sdb2.dll) - 8.0.0.2 and
> > higher
> > . ODBC (P2sodbc.dll) - 6.0.0.88 and higher
> > . OLEDB (P2soledb.dll)) - 7.0.100.37 and higher
> >
> > NOTE #1: The first 3 database drivers listed above our native drivers
> for
> > Microsoft SQL Server, Sybase, and IBM DB2 respectively.
> >
> > NOTE #2: The only Seagate Software supplied ODBC drivers that support
> > asynchronous database connection are Microsoft SQL Server and Sybase.
> CR
> > detects if an ODBC driver supports Asynchronous Query (by testing if the
> > SQL_ATTR_ASYNC_ENABLE flag on the database connection can be seen. If
> it
> > can, then it will be used (assuming the user has set the asynchronous
> > option).
> >
> > NOTE #3: P2soledb.dll checks the DBPROPSET_ROWSET property from the
> > DBPROP_ROWSET_ASYNCH property set. If this property is set, then the
> > provider accepts asynchronous queries and the option is installed.
> >
> > NOTE #4: The version numbers listed above relate to the versions of the
> > Seagate Software drivers.
> >
> >
> >
> > Support in Seagate Software Applications:
> > ============================================
> > Based on the database driver version numbers above (unless otherwise
> > noted), the following applications and DLLs support asynchronous
> database
> > connections:
> >
> > . Crw32.exe - Report Designer (at least version CR 7.0.100.15 and SI
> > 7.0.2.100)
> > . Crpe32.dll - Crystal Reports Print Engine (at least version CR
> > 7.0.100.15)
> > . RDC - Report Designer Component for Visual Basic (higher than, and
> not
> > including, version 7.0.100.15)
> > . Cipe32.dll - Seagate Info Print Engine (at least version 7.0.2.100 of
> > Seagate Info)
> >
> > CAUTION: The "Are you Finished?" message that CR sends to the database
> > server is hard coded to fire off the question for every 1-second
> interval.
> > This is not configurable.
> >
> >
> > How to Procedures:
> > ========================
> > To enable asynchronous database connections as a general option for new
> > reports:
> >
> > 1. Open the SCR Designer.
> > 2. On the 'File' menu, click 'Options'.
> > 3. Click the 'Database' tab.
> > 4. Select the checkbox 'Perform Query Asynchronously'.
> >
> >
> > To enable asynchronous database connections for existing reports:
> >
> > 1. Open the report in the SCR Designer.
> > 2. On the 'File' menu, click 'Report Options'.
> > 3. Select the checkbox 'Perform Query Asynchronously'.
> >
> > . To terminate a running query in the CR Designer, simply click the
> stop
> > button located beside the paging buttons.
> >
> > . Once a report has established a database connection, selecting or
> > clearing the 'Perform Query Asynchronously' checkbox will not take
> effect
> > until the database connection is severed and reestablished.
> >
> > . The SCR Direct Drivers for Microsoft SQL Server, Sybase and IBM DB2
> > automatically set the database connection to asynchronous mode if the
> > 'Perform Query Asynchronously' checkbox is selected.
> >
> > . The SCR Database Driver for ODBC (P2sodbc.dll) will first poll the
> ODBC
> > driver to determine if the driver in question supports asynchronous
> > database connections. If the ODBC driver supports asynchronous database
> > connections and the 'Perform Query Asynchronously' checkbox is selected,
> > the connection will be set to asynchronous mode.
> >
> > . The SCR Database Driver for OLEDB (P2soledb.dll) will first poll the
> > OLEDB provider to determine if the provider in question supports
> > asynchronous database connections. If the OLEDB provider supports
> > asynchronous database connections and the 'Perform Query Asynchronously'
> > checkbox is selected, the connection will be set to asynchronous mode.
> >
> > Availability: Public
> > Editor:CAL
> > c2006041
> >
> >
> > I hope this helps,
> > Erik L
> > id 848
> >
> > * Please note: If we may be of further assistance with this issue simply
> > reply to this email.
> >
> > You can also check the Seagate Software Knowledge Base for solutions to
> > issues similar to your own. You can find our knowledge base is at the
> > following URL:
> >
> > http://community.seagatesoftware.com/support/kbase.asp
> >
> >
> >
> >
>
> --
-- Author: Wasserman, Sara INET: sjwasserman_at_pscnet.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). --------------------------------- Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! --0-1681692777-964102508=:17351 Content-Type: text/html; charset=us-ascii <P> <BR>Actually some older versions (7.3.x?) of sqlnet didn't support async cancellation of a query. Later versions do. We use several of Quest's tools (toad, sql navigator, and sqlab xpert) and they all let you cancel a query immediately by pressing a cancel button. <P> <B><I>"Wasserman, Sara" <sjwasserman_at_pscnet.com></I></B> wrote: <BR> <BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">We use Cognos Impromptu to do ad-hoc database queries. An Impromptu user<BR>can cancel a query on the database from Impromptu. Impromptu uses SQL*net<BR>to communicate with the Oracle database. I don't know anything about<BR>asyncronous vs. synchronous, but it does sound like Seagate is trying to<BR>blame Oracle for Crystal Report's own shortcomings. A SQL*Plus or<BR>SQLWorksheet user can also cancel a query from a client. <BR><BR>Maybe you should investigate other query tools for one that will allow your<BR>users to cancel queries.<BR><BR>Sara<BR>> -----Original Message-----<BR>> From: Christine Turner [SMTP:Christine.Turner_at_IPS-Sendero.com]<BR>> Sent: Wednesday, July 19, 2000 12:00 PM<BR>> To: Multiple recipients of list ORACLE-L<BR>> Subject: RE: Asynchronous vs Synchronous<BR>> <BR>> Hello All,<BR>> <BR>> This is the response I received from my developer that ! he received from<BR>> Crystal. Anyone have any comments?????<BR>> <BR>> Thanks In Advance,<BR>> Cheers!<BR>> Christine Turner<BR>> Database Administrator<BR>> IPS-Sendero<BR>> Scottsdale, Arizona<BR>> Phone: (800) 321-6899 ext. 3286<BR>> Fax: (480) 946-8224<BR>> E-mail: christine.turner_at_ips-sendero.com<BR>> <BR>> <BR>> <BR>> -----Original Message-----<BR>> From: David Denison [SMTP:david.denison_at_ips-sendero.com]<BR>> Sent: Tuesday, July 18, 2000 3:47 PM<BR>> To: Christine Turner<BR>> Subject: Fw: CTL:20000717-10296 Automated Response: <BR>> <BR>> Here is that Crystal response concerning synchronous vs. asynchronous<BR>> database connections.<BR>> <BR>> ----- Original Message -----<BR>> To: <DAVID.DENISON_at_IPS-SENDERO.COM><BR>> Sent: Tuesday, July 18, 2000 1:32 PM<BR>> <BR>> <BR>> > This EMail was sent: 7/18/00 1:32:20 PM (Pacific Standard Time)<BR>> ><BR>> > *** This incident h! as been closed. To reopen, simply reply to this<BR>> email<BR>> > with the additional information. Do not use this Control Number for a<BR>> > different question as it will go to the wrong support group ***<BR>> ><BR>> ><BR>> --------------------------------------------------------------------------<BR>> > ------------------------------------<BR>> ><BR>> > Response To: David Denison<BR>> ><BR>> > Hi David,<BR>> ><BR>> > Thank you for using Answer by email.<BR>> ><BR>> > Unfortunately what you're trying to do will cause a gpf, and let me<BR>> > explain why.<BR>> ><BR>> > If we submit a query to your database (in this case Oracle), we send off<BR>> a<BR>> > SQL statement (i.e select * from table). Oracle processes that<BR>> statement<BR>> > and generates a dataset and passes that back to Crystal Reports to<BR>> format<BR>> > and display.<BR>> ><B! R>> > If we cancel the job or close that preview window before that data comes<BR>> > back there's no way to tell Oracle that we've cancelled that job and<BR>> it's<BR>> > going to continue sending data to memory that Crystal Reports has<BR>> already<BR>> > released back to Windows and it will crash. This bi-directional<BR>> > communication would require an asynchronous database driver on BOTH the<BR>> > Crystal Reports side of the connection and the Oracle side of the<BR>> > connection. Unfortunately, to my knowledge, Oracle doesn't support an<BR>> > asynchronous connection, and Crystal Reports only supports asynchronous<BR>> > connections with a limited number of our database drivers.<BR>> ><BR>> > I've included a Crystal Reports knowledge base article that describes<BR>> > which of our database drivers are asynchronous:<BR>> > c2006041<BR>> ><BR>> > I've also pasted this knowledg! e base article below:<BR>> ><BR>> > Asynchronous Database Connection Support for Seagate Software<BR>> ><BR>> > Product: Crystal Reports Professional Edition Version: 8.0.0.371<BR>> > Applies to: Reported version and higher<BR>> > Database: Microsoft SQL Server Platform: Windows 95 Date Verified:<BR>> > February 16, 2000<BR>> ><BR>> > Problem:<BR>> > Q: What happens when a user sends off a query in Crystal Reports (CR)<BR>> or<BR>> > in the Info Report Designer in Seagate Info (SI) and then needs to<BR>> cancel<BR>> > that query? How does the processing stop or does it even stop?<BR>> ><BR>> > Q: What is the difference between Synchronous and Asynchronous database<BR>> > connections?<BR>> ><BR>> > Q: Does Seagate Software support Asynchronous database connection?<BR>> ><BR>> ><BR>> > Solution:<BR>> > There are two possible database connection meth! ods with any type of<BR>> > database. They are:<BR>> > . Synchronous Database Connection<BR>> > . Asynchronous Database Connection<BR>> ><BR>> > An asynchronous database connection refers to the ability for a client<BR>> > application to be able to issue any number of commands to a database<BR>> > server at any given point during the database connection, without<BR>> waiting<BR>> > for the database server to complete the processing of current tasks.<BR>> ><BR>> > A primary application of asynchronous database connections, within the<BR>> > Crystal Reports (CR) Designer, is the ability to terminate a running<BR>> query<BR>> > at any point in time.<BR>> ><BR>> ><BR>> > Definitions:<BR>> > =================<BR>> > Synchronous Database Connection:<BR>> ><BR>> > Synchronous connection to a database means that once a SQL query is<BR>> passed<BR>> > to the ! database server, the calling application (Crystal Reports in this<BR>> > case) waits until it receives a "Finished" message from the database<BR>> > server. The "Finished" message is connected to the first packet of the<BR>> > result set being sent back.<BR>> ><BR>> > In Crystal Reports, if the cancel button is clicked while a synchronous<BR>> > connection is underway, the Report Designer will look as though it has<BR>> > canceled the query request. However, the request on the database server<BR>> > will continue to process until completion. Once the first packet comes<BR>> > back saying "Finished", no more of the query result set will be passed<BR>> > back.<BR>> ><BR>> > NOTE: Actually, when executing the query synchronously, Crystal Reports<BR>> > doesn't get the chance to cancel since the database client won't return<BR>> > control until the database is finished.<BR>> ><BR>> ><BR! >> > Asynchronous Database Connection:<BR>> ><BR>> > Asynchronous connection to a database means that multiple sets of<BR>> commands<BR>> > can be passed to the database server and processed at once. (For<BR>> example,<BR>> > there is no need to wait for the query to return before sending another<BR>> > command to the database server).<BR>> ><BR>> > Instead of waiting for a "Finished" message to be sent back from the<BR>> > database server, the calling application (Crystal Reports in this case)<BR>> > sends a query status message to the database server at set times asking<BR>> > "Are you done yet?" When the database server says "Yes", the result<BR>> > packets start coming back. However, if a cancel button is clicked on<BR>> the<BR>> > client computer side, instead of sending a question message to the<BR>> > database server, the client application has the ability to send a<BR>> "Can! cel<BR>> > query" message to the database server. In the Crystal Reports scenario,<BR>> > if the cancel button is clicked, instead of asking the database server<BR>> if<BR>> > it has completed its query, Crystal Reports sends a "cancel" message to<BR>> > the database server. The query never has to complete.<BR>> ><BR>> ><BR>> ><BR>> > Database Drivers that support Asynchronous Connections:<BR>> > =====================================================<BR>> > The following CR database drivers include support for asynchronous<BR>> > database connections:<BR>> ><BR>> > . Microsoft SQL Server Direct (P2ssql.dll) - 8.0.0.1 and higher<BR>> > . Sybase Direct (P2ssyb10.dll) - 8.0.0.0 and<BR>> > higher<BR>> > . IBM DB2 Direct (P2sdb2.dll) - 8.0.0.2 and<BR>> > higher<BR>> > . ODBC (P2sodbc.dll) - 6.0.0.88 and higher<BR>> > . OLEDB (P2soledb.dll)) - 7.0.100.37 and higher<BR>! > ><BR>> > NOTE #1: The first 3 database drivers listed above our native drivers<BR>> for<BR>> > Microsoft SQL Server, Sybase, and IBM DB2 respectively.<BR>> ><BR>> > NOTE #2: The only Seagate Software supplied ODBC drivers that support<BR>> > asynchronous database connection are Microsoft SQL Server and Sybase.<BR>> CR<BR>> > detects if an ODBC driver supports Asynchronous Query (by testing if the<BR>> > SQL_ATTR_ASYNC_ENABLE flag on the database connection can be seen. If<BR>> it<BR>> > can, then it will be used (assuming the user has set the asynchronous<BR>> > option).<BR>> ><BR>> > NOTE #3: P2soledb.dll checks the DBPROPSET_ROWSET property from the<BR>> > DBPROP_ROWSET_ASYNCH property set. If this property is set, then the<BR>> > provider accepts asynchronous queries and the option is installed.<BR>> ><BR>> > NOTE #4: The version numbers listed above relate to the vers! ions of the<BR>> > Seagate Software drivers.<BR>> ><BR>> ><BR>> ><BR>> > Support in Seagate Software Applications:<BR>> > ============================================<BR>> > Based on the database driver version numbers above (unless otherwise<BR>> > noted), the following applications and DLLs support asynchronous<BR>> database<BR>> > connections:<BR>> ><BR>> > . Crw32.exe - Report Designer (at least version CR 7.0.100.15 and SI<BR>> > 7.0.2.100)<BR>> > . Crpe32.dll - Crystal Reports Print Engine (at least version CR<BR>> > 7.0.100.15)<BR>> > . RDC - Report Designer Component for Visual Basic (higher than, and<BR>> not<BR>> > including, version 7.0.100.15)<BR>> > . Cipe32.dll - Seagate Info Print Engine (at least version 7.0.2.100 of<BR>> > Seagate Info)<BR>> ><BR>> > CAUTION: The "Are you Finished?" message that CR sends to the database<BR>> > ser! ver is hard coded to fire off the question for every 1-second<BR>> interval.<BR>> > This is not configurable.<BR>> ><BR>> ><BR>> > How to Procedures:<BR>> > ========================<BR>> > To enable asynchronous database connections as a general option for new<BR>> > reports:<BR>> ><BR>> > 1. Open the SCR Designer.<BR>> > 2. On the 'File' menu, click 'Options'.<BR>> > 3. Click the 'Database' tab.<BR>> > 4. Select the checkbox 'Perform Query Asynchronously'.<BR>> ><BR>> ><BR>> > To enable asynchronous database connections for existing reports:<BR>> ><BR>> > 1. Open the report in the SCR Designer.<BR>> > 2. On the 'File' menu, click 'Report Options'.<BR>> > 3. Select the checkbox 'Perform Query Asynchronously'.<BR>> ><BR>> > . To terminate a running query in the CR Designer, simply click the<BR>> stop<BR>> > button located beside the paging bu! ttons.<BR>> ><BR>> > . Once a report has established a database connection, selecting or<BR>> > clearing the 'Perform Query Asynchronously' checkbox will not take<BR>> effect<BR>> > until the database connection is severed and reestablished.<BR>> ><BR>> > . The SCR Direct Drivers for Microsoft SQL Server, Sybase and IBM DB2<BR>> > automatically set the database connection to asynchronous mode if the<BR>> > 'Perform Query Asynchronously' checkbox is selected.<BR>> ><BR>> > . The SCR Database Driver for ODBC (P2sodbc.dll) will first poll the<BR>> ODBC<BR>> > driver to determine if the driver in question supports asynchronous<BR>> > database connections. If the ODBC driver supports asynchronous database<BR>> > connections and the 'Perform Query Asynchronously' checkbox is selected,<BR>> > the connection will be set to asynchronous mode.<BR>> ><BR>> > . The SCR Database Driver for! OLEDB (P2soledb.dll) will first poll the<BR>> > OLEDB provider to determine if the provider in question supports<BR>> > asynchronous database connections. If the OLEDB provider supports<BR>> > asynchronous database connections and the 'Perform Query Asynchronously'<BR>> > checkbox is selected, the connection will be set to asynchronous mode.<BR>> ><BR>> > Availability: Public<BR>> > Editor:CAL<BR>> > c2006041<BR>> ><BR>> ><BR>> > I hope this helps,<BR>> > Erik L<BR>> > id 848<BR>> ><BR>> > * Please note: If we may be of further assistance with this issue simply<BR>> > reply to this email.<BR>> ><BR>> > You can also check the Seagate Software Knowledge Base for solutions to<BR>> > issues similar to your own. You can find our knowledge base is at the<BR>> > following URL:<BR>> ><BR>> > http://community.seagatesoftware.com/support/kbase.asp<BR>> ! ><BR>> ><BR>> ><BR>> ><BR>> <BR>> -- <BR>-- <BR>Author: Wasserman, Sara<BR>INET: sjwasserman_at_pscnet.com<BR><BR>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051<BR>San Diego, California -- Public Internet access / Mailing Lists<BR>--------------------------------------------------------------------<BR>To REMOVE yourself from this mailing list, send an E-Mail message<BR>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in<BR>the message BODY, include a line containing: UNSUB ORACLE-L<BR>(or the name of mailing list you want to be removed from). You may<BR>also send the HELP command for other information (like subscribing).</BLOCKQUOTE><p><br><hr size=1><b>Do You Yahoo!?</b><br>Received on Thu Jul 20 2000 - 09:15:08 CDT
 |
 |