Hi Guys,
This question might test the memory to remember but I am in the process on upgrading a site on Jiwa 6.4.3 to Jiwa 7
In 6.4.3 the PO_Main table looks like
CREATE TABLE [dbo].[PO_Main](
[OrderID] [char](20) NOT NULL,
[LastSavedDateTime] [datetime] NULL,
[CreditorID] [char](20) NOT NULL,
[OrderNo] [varchar](15) NOT NULL,
[OrderedDate] [datetime] NOT NULL,
[Header1] [varchar](255) NULL,
[Header2] [varchar](255) NULL,
[Header3] [varchar](255) NULL,
[Header4] [varchar](255) NULL,
[Header5] [varchar](255) NULL,
[ContactType] [smallint] NOT NULL,
[Status] [smallint] NOT NULL,
[OrderType] [smallint] NULL,
[OrderTypeInvID] [char](20) NULL,
[OrderTypeInvDetails] [varchar](100) NULL,
[IN_LogicalID] [char](20) NOT NULL,
[OrderSupplierType] [smallint] NOT NULL,
[CentralWarehouseID] [char](20) NULL,
[TaxTotal] [float] NULL,
[CurrencyID] [char](20) NULL
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
and in Jiwa 7
CREATE TABLE [dbo].[PO_Main](
[OrderID] [char](20) NOT NULL,
[LastSavedDateTime] [datetime] NULL,
[CreditorID] [char](20) NOT NULL,
[OrderNo] [varchar](15) NOT NULL,
[OrderedDate] [datetime] NOT NULL,
[Header1] [varchar](255) NULL,
[Header2] [varchar](255) NULL,
[Header5] [varchar](255) NULL,
[Status] [smallint] NOT NULL,
[OrderType] [smallint] NULL,
[OrderTypeInvID] [char](20) NULL,
[IN_LogicalID] [char](20) NOT NULL,
[OrderSupplierType] [smallint] NOT NULL,
[CentralWarehouseID] [char](20) NULL,
[TaxTotal] [decimal](19, 6) NULL,
[CurrencyID] [char](36) NULL,
[InTransitWarehouseID] [char](20) NOT NULL DEFAULT (''),
[Reference] [varchar](50) NULL,
[PO_Workflows_RecID] [char](36) NOT NULL,
[HR_Staff_RecID] [char](20) NULL,
[CR_Warehouse_WarehouseID] [char](36) NULL,
CONSTRAINT [PK_PO_Main] PRIMARY KEY NONCLUSTERED
(
[OrderID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
As can be seen fields Header3 and Header4 have disappeared in the process as has the data in them, the problem also is that the original customisation used these two fields as part of a reporting system, so my question is has the data been lost or moved in the upgrade process and what would be the best way of avoiding this and possibly other similar issues given the age of this database?