We having a problem adding a MFS to tables with Error X105 using the MFS_Installer program. Can you please assist with this. The program below is being used for adding the MFS. The error occurs when performing the action to the MFS.

compile Subroutine install_mfs(nul)

    TargetTable=U_PRODUCTS'

    MFSName    =PRBAL_MFS*ARCADIA'

    Action     =2

    call MFS_Installer(TargetTable,MFSName,Action)

Return

*——————————————————————-

Compile subroutine MFS_Installer(TargetTable,MFSName,Action)

/*

–] RUN MFS_INSTALLER 'CUSTOMERS','SIMPLE_MFS*EXAMPLES',2 ,1) Else

          MFSName :=*':@AppID

    End

/* first remove MFS (in case it is already in the media map)*/

    Set_Status(0)

    Set_MFS(TargetTable, MFSName, 5)

    Convert @Lower_Case to @Upper_Case in Action

    If Action=5 or Action=REMOVE' then

          Return

    End

* perform action to the MFS

    Set_Status(0)

    Set_MFS(TargetTable, MFSName, Action)

    if Get_Status(Code) then

          Error=An error occurred adding the MFS to the ": TargetTable: " table."

          Error := "||Error Code: ": Code

          call obj_msg(Error)

    end

/* update database definition*/

    Set_Status(0)

    Define_Database(@DBID,1,"","")

    if Get_Status(Code) then

          Error=An error occurred saving the ": @dbid: " database definition."

          Error := "||Error Code: ": Code

          call obj_msg(Error)

    end

Return

*—————————————————————-

Why not use SET_MFS from TCL or from the Database Manager - File -] MFS Table Control?

Thank you for response,

I tried adding from Database Manager -] MFS Table control but am getting this error message: Any idea what could be wrong. Thank you in advance,

ps We have created the MFS in sysprog CHANGE.MFS

FS10: Domain validation error. The record "%1%" contains illegal characters - or - the data does not pass validation patterns specified in the dictionary.

can you name it CHANGE_MFS ?

Is your custom MFS, called "CHANGE.MFS", calling the next mfs? I think I remember that this issue is caused by not calling the next mfs.

View this thread on the Works forum...