PDW: Performing operation, then updating record

PDW: Performing operation, then updating record

Post by Robert Hanki » Fri, 18 Aug 1995 04:00:00



In PDW, we would like to have the ability to enter new orders (records), then
whenever desired throughout the day, batch print all orders which have not
been printed previously.  We don't want to use a date to determine which
records to print as we desire to be able to print these new records at more
times that once during the day.

In order to do this, we are considering adding a field to our table that would
be blank at the time the order is entered, then programming a button that
would locate all records in which this field was blank (or could be a certain
status number), then print these new records, then change the field in each of
these records in order to indicate that they had been printed.

Is this the best way to accomplish this task or are there better or simpler
ways to accomplish this task.  All suggestions will be appreciated!  Feel free
to post or e-mail any responses.

Thanks in advance.

Bobby Hankins

 
 
 

PDW: Performing operation, then updating record

Post by Kuo-Sheng (Kas » Wed, 23 Aug 1995 04:00:00


: In PDW, we would like to have the ability to enter new orders (records), then
: whenever desired throughout the day, batch print all orders which have not
: been printed previously.  We don't want to use a date to determine which
: records to print as we desire to be able to print these new records at more
: times that once during the day.

: In order to do this, we are considering adding a field to our table that would
: be blank at the time the order is entered, then programming a button that
: would locate all records in which this field was blank (or could be a certain
: status number), then print these new records, then change the field in each of
: these records in order to indicate that they had been printed.

: Is this the best way to accomplish this task or are there better or simpler
: ways to accomplish this task.  All suggestions will be appreciated!  Feel free
: to post or e-mail any responses.

Well, I would use a Logical or A1 field instead. Just mark the ones you
want to print, then print only those, and those printed will be UNmarked.
This way you don't have to mess with the timestamp if you want to reprint
something.

--
=========================================================================
Kasey K. S. Chang (a guy)             | Paradox for Windows Programmer

URL> http://userwww.sfsu.edu/~kschang | X-COM Guru   General PC expert
--------------------------------------+----------------------------------
Editor of XCOM and XCOM2 UN-official Strategy Guide -- FREE!  (See URL)

 
 
 

1. Can't perform operation with an async operation pending

Has anyone come across the error message, "ComFailException: Can't perform
operation with an async operation pending"

I have a WFC Client that opens multiple DataControl recordset to a
RDS.DataFactory in Asynchronous mode.

When I modify some fields in one of the recordsets and try to SubmitChanges
back to the server I the this error message.

I use a separate DataControl for each recordset, 12 to be exact, and all are
async.

--
William MacDonald
Intellect Systems Inc.
Ontario, Canada
http://www.hrintellect.com/

2. job opening

3. Could not perform update because another user changed the record using SQL server

4. > BLOCK-PRINT AND GOO

5. Help needed fast - pdw 4.5 --> pdw 5.0

6. Need help with linkedserver

7. Going from PDW 1.0 to PDW 4.5?

8. create query

9. Setup failed to perform required operations on the cluster nodes

10. setup failed to perform required operations on the cluster node

11. setup failed to perform requested operation on cluster nodes

12. RUNDLL32 performed illegal operation error