Sequence conversion

Hello:
I am trying to convert a LabWindows/CVI sequence file to TestStand but
I get warnings/errors when opening or running the sequence in TestStand.
After converting the file I do a File->Open in the TestStand Sequence
Editor and I get a "Open Sequence Warning" popup listing a bunch of items
it was unable to load due to undefined references.
When I attempt to run the sequence I get the following error:
Unable to get standard CVI step module address.
A CVI code module has unresolveable external references.
Error Code: -17709
The sequence file is pointing to an OBJ file. Do I have to rebuild the
object file prior to conversion or something?
We are attempting to migrate from CVI to TestStand and there will be a
lot of sequenc
e conversion taking place. I am doing the pilot and trying
to document the procedure.
The User Manual, page 4-31, says to refer to the online help under
"Converting From the Labwindows/CVI Test Executive to TestStand" but
I couldn't find anything in the windows help file or on the net.
Thanks for any help.
-Steve
Steve Heitke Tellabs Operations, Inc.
[email protected] Advanced Test Methods
http://www.tellabs.com Bolingbrook, IL 60440

Steve,
Your object files probably depend on other object files or support libraries
that haven't been loaded. When you ran from the test executive, you included
them in the CVI project so they were preloaded.
TestStand is a little different because it isn't a CVI project that you build
into an application. Instead, you need to configure the CVI adapter to pre-load
your support libraries. Select Configure>>Adapters. Select the CVI Std
Prototype Adapter and click Configure. In the CVI Std Adapter Configuration
dialog, press the Configure Auto-Loading of Support Libraries Needed for
linking Objs and Libs. Add all your support libraries to this dialog. TestStand
will copy your files to the TEstStand\AdapterSupport\CVI\AutoLoadLIbs directory
where they can be preloaded.
It is often tricky to figure out which support libraries you need. For this
reason, NI and Microsoft encourage people to use DLLs instead. DLLs can
be loaded dynamically, and by default, the OS loads them for you. Usually,
you just leave DLLs in the same directory as the executable or the WIndows\System32
(\System for Win95/98).
Let us know if this doesn't work out.
Paul Mueller
National Instruments
Steve Heitke wrote:
>Hello>I am trying to convert a LabWindows/CVI sequence file to TestStand
but>I get warnings/errors when opening or running the sequence in TestStand.>>After
converting the file I do a File->Open in the TestStand Sequence>Editor and
I get a "Open Sequence Warning" popup listing a bunch of items>it was unable
to load due to undefined references.>>When I attempt to run the sequence
I get the following error> Unable to get standard CVI step module address.>
A CVI code module has unresolveable external references.> Error Code:
-17709>>The sequence file is pointing to an OBJ file. Do I have to rebuild
the>object file prior to conversion or something?>>We are attempting to migrate
from CVI to TestStand and there will be a>lot of sequence conversion taking
place. I am doing the pilot and trying>to document the procedure.>>The User
Manual, page 4-31, says to refer to the online help under>"Converting From
the Labwindows/CVI Test Executive to TestStand" but>I couldn't find anything
in the windows help file or on the net.>>Thanks for any help.>>-Steve>--
>________________________________________________________________________>
Steve Heitke Tellabs Operations, Inc.> [email protected]
Advanced Test Methods> http://www.tellabs.com
Bolingbrook, IL 60440>________________________________________________________________________

Similar Messages

Script to sequence conversion

Hi,
I would like to know if it would be possible to convert a text based test script to a TestStand sequence? The conversion program would be developen with LabVIEW.
The test script would have a syntax similar to Perl. We would like to be able to declare variables, include for, if-then-else and while statements.
For example a non TestStand programmer could write this script:
$count = 10;
$instrumentAnswer
instrumentAnswer = ReadInstrument(0,1)
while ($instrumentAnswer >= 0 and count >= 0) {
WriteInstrument(0,1)
instrumentAnswer = ReadInstrument(0,1)
WriteInstrument(2,10)
instrumentAnswer = ReadInstrument(6,0)
$count--;
Do you think it is possible and do you have any hints on how to do this?
Thanks!
-M

Hi M,
It sounds like the hint that you're looking for is most likely a Sequence File Translator. This tool allows you to load sequence files with your own custom file formats. There's a good 16 pages of information about how to implement these that can be found in Chapter 15 of the TestStand Reference Manual. You can find this manual by going to: Start»Programs»National Instruments»TestStand 4.0»Online Help»Manuals»TestStand Reference Manual.
Here's also another long thread on this issue that you might find useful:
http://forums.ni.com/ni/board/message?board.id=330&message.id=17873&requireLogin=False
Have a good day!
Lars

24p to a 30 fps sequence conversion

24P to 1080i/30fps
Hello everyone. I am trying to combine footage shot on the SDX 900 at 24p with footage shot on the HPX 500 at 1080i/30fps
My sequence is 30 fps.
The 24p looks jerky & I am not sure what to do.
Does anyone have any suggestions?
Regards
Bonnie

So you are mixing SD and HD in the same sequence.
The SDX 900 shot at 24P actually prints to tape at 29.97 inserting a 2:3 pulldown for a "Film Look"
Depending on how it was captured it is natively 720x480 interlaced at 29.97 and will have a judder to the footage due to shooting format. The HPX shot at 1080i30 will be native 1080 x 1440 at 29.97 fps with no pulldown.
If you have access to a Kona capable of upconversion or MatroxMXO2 you can upconvert the SDX footage to 1080 on input and maintain a DVCProHD1080i 29.97 codec. It upconverts quite nicely however it will still have a 2:3 puldown. If you don't have access to a capture card upconvert you could drop in your selects from the SD footage into compressor and convert via software to dvcProHD 1080i with a 29.97 timebase

What are the conversion rules

what are the conversion rules?can anybody give information on that?points wil be rewarded?

hI..
From sap help....
Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character

Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion

C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.

Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
Conversion rules for internal tables:
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
Conversion Rules for Structures
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Message was edited by:
Rammohan Nagam

Frame Rate Conversion Question...

I have a bit of a mess here. I shot a film on the Canon XL2 at 24p. I digitized the footage in my old Avid system as a 23.976fps project and edited the entire movie. When I burned the movie to disk it had all kinds of skipping problems with the image. I wasn't sure what I had done wrong because if you shoot at 24p it should have been fine as a 23.976 project in Avid. But the XL2 apparently records at 23.976 fps, while inserting 6 frames every second to create a 30fps master tape. So I was supposed to import the footage into a 30i project. I've subsequently shot a short on the XL2 and digitized it at 30i and it turned out fine.
So here's my question. I have since switched over to FCP and I know with Automatic Duck I can convert the project from an Avid to a FCP project. However, I'm still going to have the frame rate problem. Does anyone know what my options are here? Is it possible to create a 30i project, bring in the 23.976 sequence and recapture the footage at the correct frame rate?

I have since switched over to FCP and I know with Automatic Duck I can convert the project from an Avid to a FCP project.
Automatic Duck doesn't do project conversions. Only sequence conversions. It won't do all the media, or bins. Only the media in a sequence.
Shane

Conversions in abap

Hi
I want to know what are the conversions and what are the different types of conversions in abap
Regards
Pavan

Hi
A conversion means data that is converted from one format to another format and from one system to another. So when you first implement SAP, you are actually replacing some of your legacy systems, but you are not completely trashing the data. You still need some of that data from the systems that are being replaced. So you pull the data out of your legacy systems and put them on some files. You then want to load that data into your new SAP system. That is when you write some programs which will read that data and load it into SAP. Imagine you had a home grown purchasing system. You are now replacing all that with SAP. But until SAP goes live, you want to keep using your home grown purchasing system. So during go live, you want to transfer the POs from your legacy system to SAP. Now a PO in your legacy system may not have the same fields as a PO in SAP. So you convert the data.
from sap help....
Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character
Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion
C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.
Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
Conversion rules for internal tables:
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
Conversion Rules for Structures
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Don't forget to reward if useful...

Capturing SD anamorphic at 60 fps?

I made a custom capture preset for DV Anamorphic with a 60 frame rate, since there was no preset for this. But when I capture the clips display as 29.97 fps.
Does FCP not work with SD @ 60 fps? If not, I'm confused why the manual setting is even an option.
If it is possible to capture at this frame rate in SD please help me out.
thanks.

So Shane
A quick question in the same vein [2 parts].
Using a Sony HDR-FX1E HDV camera we want to achieve something in the order of filming at either 50 or 100 frames per second. Given our equipment limitations will shooting 1440x1080 at 50i with a shutter speed of 1/200 achieve anything like 100 frames per second shot. We, like Macongaman, are hoping to produce a shot that has more detail and less motion blur when its speed is slowed considerably in FCP?
And just as important would you still digitise the footage using either of FCP's following Capture Presets?
AJA Kona 3: 1080i 25 Apple ProRes 422 [even though the colour space is 420 for PAL HDV and the pixel res for this preset is 1920x1080 - no option for 1440]
and/or
HDV-Apple ProRes 422
And then edit into a Sequence with either of the following settings [for best real time performance and nil in-sequence conversions [in order of assumed preference]]?
AJA Kona 3: 1080i 25 Apple ProRes 422 [1920x1080]
and/or
Apple ProRes 422 1440x1080 50i 48kHz
and/or
HDV - 1080i50
and/or
Apple Intermediate Codec 1080i50
I know the first part of the question is geared toward a DV Rebels type forum but given your obvious knowledge on shooting it [or having this kind of footage delivered to you] and then dealing with it in post I thought it best to ask here.
And if anyone else can contribute to this also it would be greatly appreciated. Thanks.

How to covert field in abap

hi all,
i have to concert 100 into decimal.
can you please tell me the procedure

Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character
Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion
C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.
Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.

I accidentally deleted an email. How can I restore.

When selecting an email to open I accidentally clicked on the bin symbol. Can and how I restore.
I would appreciate your help as it is an important email for me . It is the first in a sequence conversation.
Thank You
Nancy

Hi!
Usually, you can click on the Trash folder, locate the email you deleted, and then right-click on it or drag it to restore it to your original location.
If you need more specifics:
Would you please clarify which email service (Gmail, Yahoo!, Outlook.com, etc.) you are using? Are you using Thunderbird?
<hr>
I hope that solved your problem!
If it did, would you please choose this answer as your solution? It would help other Firefox users to find help on the forums faster and more efficiently. Thanks!
And of course, feel free to post back if you need more help!
Happy browsing!

Robohelp 9, framemaker 10 conversion not in sequence of chapter but in alphabetic order of .fm files

Hi All,
We are trying to do the following :
- Create a Frame maker Book with a couple of chapters & TOC
- Import the Book into RoboHelp
- Save the document in RoboHelp to PDF, WebHTML & EPUB
- The output files are created but we do not see the content as expected.
Platform/Tools - Windows XP , Framemaker 10 , Robhelp 9
Issues :
PDF - The Chapters are ordered in the alphabetical sequence rather than the Chapter/Page sequence set by using the Numbering option for Chapter/Page - "Continue numbering from previous page in book".
WebHTML - The TOC does on the left frame/pane does not show the list of chapters
- The Chapters are ordered as per the alphabetical numbering ( Chapters begining with Numbers then alphabets etc.) rather than the order seen in Framemaker
EPUB - The TOC shows the numbers which are again ordered in alphabetical order but not reflecting the actual order of the chapters seen in framemaker.
- The Chapters are ordered as per the alphabetical numbering ( Chapters begining with Numbers then alphabets etc.) rather than the order seen in Framemaker
Could the folks are experienced with document publishing using Framemaker guide appropriately.
Thanks in Advance

Ok, wrong forum - you should be in the FrameMaker Integration thread in the RH forum, but no matter.
Trying to create PDF output out of RH will drive you crazy since you have to go through Word to get to PDF. Much better to go to PDF straight from your FM source book. This is one of FM's strengths - it's not one of RH's.
Since all your issues seem to stem from your ToC, I would recommend messing around with it in FM to get it looking correct. Then import the content & ToC into RH. The "Edit FM documents" button in the Conversion Settings dialog allows you to bring over your FM ToC into RH; they also control how content will appear and how topics are to be created (pagination).
If, after importing, your ToC in RH isn't what you want it to look like, just edit it within RH - since you're importing FM content (not linking) each time you import it's a fresh start (and new project). You can easily move stuff around in a RH ToC.

Trouble exporting 320x240 from 720x480 sequence using QT conversion

(Opps, put this on the FCP Express discussion 1st...)
Hi,
Everytime I try to export a 720x480 sequence from FCP with "using QT Conversion" to a 320x240 size, it exports out as 640x480. Everytime. Used to work just fine. Same thing happens using a compressor setting to 320x240 and exporting right from the QT export size setting. Anyone know what gives? I tried trashing prefs in both FCP and QT. No luck.
Thanks!

This is the first time I've heard of this problem so no real basis to go on. Try the QT prefs delete again and if not that, then the QT reinstall.
To do a full quicktime reinstall.
Go to /library/receipts and delete any files that say Quicktime followed by a number e.g. Quicktime703.pkg
Go to the Apple quicktime site and download the appropriate version of Quicktime to your hard drive.
Run the Quicktime installer.
Repair Disk Permissions for your System Disk (Disk Utility > Select the system disk > Repair Disk Permissions)
Reboot
Good luck.
x

UoM in sequence of conversion factor

Hi Friends,
Need Help!!!!
Is there any function module or a program with which I can determine the sequence of units of measure. It can be achieved programatically but looking for some ready to use API.
For Example :
1 CS = 10 EA
1 BX = 2 EA
1 DZ = 12 EA
1 EA = 1 EA
Then my sort sequence should look like below
1 EA = 1 EA
1 BX = 2 EA
1 CS = 10 EA
1 DZ = 12 EA
This is a simple example but there could be some complicated scenarios as well.
Thanks

Hi,
Use FM CRS_MATERIAL_READ_ALL.
Table ET_MARM will give you the UoM conversion routines for the material.
Regards,
Jovito

SWF conversion in images sequency (JPGs, GIF, MNG...)

Hello,
I have some SWF files to convert in MNG animation or images sequencies.
(my developped software does not support SWF files. Alas!).
To do that, I am looking for a reliable tool allowing either:
- to convert SWF in MNG,
- or to extract sequencies of pictures (PNGs, JPGs...), in order to build a MNG file after this step (thanks another soft).
The SWF durations are 4s-8s, at 12fps.
They are composed by just a frame (which is containing some images which are moving in loop; no interactive content).
I tried to export an animation file with Adobe Flash CS4 with a SWF file, or a FLA file : it has not been successful.
I tried some tools which seems working by 'screenshots' of the SWF frame : I have some results, but not very good.
I do not have the Flash project which has been used to create SWF, but I can ask to my SWF provider some additionnal files which could be useful for my need (he is not an expert).
So, I do not have any solutions for that (Adobe tool? Another?).
Thanks for you help.

Here's what my .htaccess file looks like. Don't know if it makes a difference, but all the rewrite engine commands are within an IfModule tag.
<IfModule mod_rewrite.c>
RewriteEngine on
# This condition would allow access from no referrer
# Remove the hash if needed
# RewriteCond %{HTTP_REFERER} !^$
# Allow access from mydomain.com and www.mydomain.com
RewriteCond %{HTTP_REFERER} !^http://(www.)?mydomain.com/.*$ [NC]
# Allow access from mydomain.com and www.mydomain.com on port 12854
RewriteCond %{HTTP_REFERER} !^http://(www.)?mydomain.com:12854/.*$ [NC]
# file types to control
RewriteRule \.(gif|jpe?g|png)$ - [F]
</IfModule>

Conversion of Java Generics to JavaFX sequence in Java Program

I have created a TwitterFetcher.java which collects the latest 20 tweets and generates a List<TwitterUpdate>
I know that I have to convert this Java List into a JavaFX Sequence using Sequences.
Have tried quite a few variations with Sequences.make(...) but to no avail.
following is the code:
import com.sun.javafx.runtime.sequence.Sequence;
import com.sun.javafx.runtime.sequence.Sequences;
import java.util.Iterator;
import org.w3c.dom.TypeInfo;...
List<TwitterUpdate> ltu = new ArrayList<TwitterUpdate>();
TwitterUpdate tu = new TwitterUpdate();
Sequence<? extends TwitterUpdate> stu;
public Sequence<TwitterUpdate> getUpdates()
for (Status status : api.getFriendsTimeline())
tu.setName(status.getUser().getName());
tu.setScreenName(status.getUser().getScreenName());
tu.setImgURL(status.getUser().getProfileImageUrl());
tu.setTweet(status.getText());
tu.setDate(status.getCreatedAt().toDate().toString());
ltu.add(tu);
//convert the List to a Sequence
//return the sequenceAm I missing a step or two or doing something completed wrong.??
I really have to get this done..

We are actually following MVC architecture, where in our back end is totally in Java and the rendering is handled in JavaFX..
Hence interop between the two was extremely important..
and the problem was that...
in our JavaFX project...we have packages with only java files and other packages with only JavaFX package..
So whilst importing packages in a JavaFX classes..we can recognize our own java and javafx files...
But whilst in Java classes..recognition of Javafx packages is not possible....
Hence sharing Data structures between the two was difficult...
So we ended up making POJOs..and ported that in JavaFX classes as it was able to recognize Java objects...
We are now using concept of Array of objects and passing it to JavaFX classes as return type..
Regards
Kaustubh

Word to pdf conversion sequence

Pllease advise how to fix the problem when converting a document from to pdf. It opens last page first in pdf.....

How are you trying to convert to PDF from WORD? If you are printing, have you checked the WORD settings that allow you to print in reverse order?

Sequence conversion

Similar Messages

Maybe you are looking for