Converting 4D View documents

Home

4D v17

You can convert your 4D View documents to 4D View Pro areas using the VP Convert from 4D View command. Most properties and information stored in 4D View documents are automatically converted, including formats, styles, borders, values, formulas, selections, zoom, etc. In general, converted 4D View documents will be rendered in 4D View Pro areas exactly as they were rendered in 4D View areas, like the following:

Original 4D View document:

Document converted in 4D View Pro area

We are doing our best to ensure that converted documents remain as true as possible to the original, but some features may not be fully rendered. These are described in the paragraph below.

Conversion process

Note: The 4D View document conversion feature is being continuously improved, based on customer feedback. It is highly recommended to always keep a copy of your original 4D View BLOBs or documents, even after a successful conversion.

With regards to the current state of your 4D View plug-in document, the conversion process requires the following steps.

Load your 4D View document (.4pv) into a BLOB:
Note: If your 4D View document is already stored in a BLOB field, go to step 2.
C_BLOB($pvblob) DOCUMENT TO BLOB("document.4PV";$pvblob)
Call the VP Convert from 4D View with the BLOB containing the 4D View document:
C_OBJECT($vpObj) $vpObj:=VP Convert from 4D View($pvblob)
Assign the resulting object to a 4D View Pro area form object or a document to see the results.
VP IMPORT FROM OBJECT("4DViewProArea";$vpObj)

Conversion details

The following table provides the current status for the primary conversion areas. Note that this list will be updated regularly, as the conversion process is continuously improved.

Feature	Conversion status	Comments
Document attributes	Document display attributes are converted: selected cells, zoom, grid display.
	Document information is converted: version, title, subject author, company, note, creation and modification date.
Columns and rows	All defined columns and rows are converted with their original size.
	Column and row headers are converted without any restrictions.
Borders	Borders are converted with their thickness and color. Grid display settings are converted.	Only one single bar border and one double-bar border models are available in 4D View Pro. Single bar borders are converted the same as the original, any double-bar borders are converted to the 4D View Pro double-bar model.
Splitters	Currently not converted
Styles & fonts	Styles and style sheets are converted. Conditional styles are not supported.	Deprecated text styles (i.e. Shadow, Condensed, etc.) and QuickDraw fonts are not converted.
	Rotation styles (oriented text) are currently not converted
Formats & cell names	Cell formats are converted to available formats with similar rendering. All data type formats are supported: text, number, date and time, boolean, picture. Cell names are converted.	Format conversion could give unexpected results for some documents because formats sometimes rely on system settings (i.e. for the decimal separator) and may have been defined globally or separately.
	User defined 4D formats (starting with "\|") are currently not converted
	Controls created with PV SET CELL CONTROL (button / radio button / check box / drop down / combo box) are currently not supported
Pictures	Pictures are supported and converted with some limitations	4D View picture format included multiple codecs and is deprecated. Converted pictures keep only the most appropriate codec for html rendering (svg, png, jpeg, gif) and are saved in base64.
	Pictures with truncated centered / replicated format are currently not converted	Background pictures are not replicated on each page (this concept does not exist in 4D View Pro).
Printing	Currently not supported	Printing options and print settings defined in the 4D View document are converted.
Dynamic links	Cells or columns linked to fields or variables are currently not supported
Formulas	Formulas are converted but references to 4D commands, methods, variables and fields are currently not supported