No! They are based on a chosen date from a popup calendar.

I am in the midst of tracing the code and for some reason here is what
is happening.

The first cursor captures the order number.

The second cursor captures the number of pieces (this will tell how many
labels to print for this order)

When the number of labels are done being processed (based on number of
pieces) the first cursor is supposed to grab the next order.

 

Right now it is not changing the order number in the first cursor.

So what seems to be happening is the while loop never closes since it
never goes on to the next order.

It keeps cycling through the second cursor (number of packages) but
always uses the same order number instead of going to the next one.

 

The confusing thing is it works for a different day.

 

James Belisle

 

Making Information Systems People Friendly Since 1990

 

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of jan
johansen
Sent: Wednesday, June 20, 2012 3:41 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: labels not showing

 

The labels aren't based on .#DATE are they?

         

        -----Original Message-----
        From: "Jim Belisle" <[email protected]>
        To: [email protected] (RBASE-L Mailing List)
        Date: Wed, 20 Jun 2012 15:36:32 -0500
        Subject: [RBASE-L] - labels not showing

        I have a strange problem with labels not showing for a specific
date.
        
        If we run a command file bringing up today's Bill of Lading
shipping
        labels the command works fine.
        
        The labels show to our screen and then we print them.
        
         
        
        If I run the same command file for tomorrow's date 06/21/2012,
RBASE
        freezes up.
        
        I have tried this on three different computers, including one
remotely
        and the same thing happens.
        
        If I try bringing up a specific BOL on this date 06/21/2012, it
comes up
        on a form and we can print the labels.
        
         
        
        This command file is a cursor file run with a while loop WHERE
SQL <>
        100.
        
        Any suggestions as to where I should look?
        
         
        
        James Belisle
        
         
        
        Making Information Systems People Friendly Since 1990
        
         
        
         
        
         
         

Reply via email to