Options

Error when transfering objects

JavaidJavaid Member Posts: 23
Hi

Can someone tell me why we sometime get error when we transfer objects from developer database to live database. NAS service has been restarted.

The objects from developer has been complied correctly.

See the attachment.

Thanks.



Best Recards
Javaid

Comments

  • Options
    Jan_VeenendaalJan_Veenendaal Member Posts: 206
    One way to get this kind of errors is:
    1. In DEV database: Create function x in table T
    2. In DEV database: Use function x on page P
    3. Transfer both table T and page P to other database
    4. In DEV database: Remove function x from table T
    5. In DEV database: compile only table T. You will get no compile error
    6. Transfer table T to other database using fob file. You will not get an error
    7. In other database, open page P

    (actually page P will of course give an error in your DEV db, too)

    So if you delete any non-local function, or table field, then you need to make sure that ALL objects that reference that function/field are updated too.
    Jan Veenendaal
  • Options
    mdPartnerNLmdPartnerNL Member Posts: 802
    One way to get this kind of errors is:
    1. In DEV database: Create function x in table T
    2. In DEV database: Use function x on page P
    3. Transfer both table T and page P to other database
    4. In DEV database: Remove function x from table T
    5. In DEV database: compile only table T. You will get no compile error
    6. Transfer table T to other database using fob file. You will not get an error
    7. In other database, open page P

    (actually page P will of course give an error in your DEV db, too)

    So if you delete any non-local function, or table field, then you need to make sure that ALL objects that reference that function/field are updated too.

    So compile all objects were modified=yes is enough?
  • Options
    Jan_VeenendaalJan_Veenendaal Member Posts: 206
    @mdPartnerNL:

    No. Since the modified flag could have been reset it is not enough to compile only objects where modified=true.

    First step is to compile ALL objects. But even then you cannot be sure since (table fields) could also be referenced by fieldnumber. This kind of reference will only throw an error when the code is actually executed.

    Key thing is that when you change something in your environment you need to know, BEFORE changing anything, what the impact will be....
    Jan Veenendaal
Sign In or Register to comment.