Visual LANSA Forum

Thanks Tom, there were some very good pointers in that example, though it uses a Tree view. I needed to use a Grid or List view, so I used that example to come up with a working example. Here it is:

Function Options(*DIRECT)
Begin_Com Role(*EXTENDS #PRIM_FORM) Caption('Drag and Drop') Height(491 ...

I have been trying to write a simple VL Form that shows how to move a grid list entry within the displayed list by simply dragging and dropping the entry from one location to another. So far, I have not been able to make things work. I am unable to retrieve the current row number where the drop will ...

You should log that observation with the LANSA Support desk. The objects should show up on your list automatically as they already belong to the specified TASK_ID. Looks like a minor defect as you already have a workaround (Master refresh).

Are you using Repository Synchronization in this environment? How are the objects being propagated to the second developers repository?

There must be multiple ways of doing this. Here is one possible way:

Begin_Com Role(*EXTENDS #PRIM_WEB) Layoutmanager(#Layout1) Height(545) Width(897)
Define_Com Class(#PRIM_TBLO) Name(#Layout1)
Define_Com Class(#PRIM_TBLO.Column) Name(#Column1) Displayposition(1) Parent(#Layout1)
Define_Com Class ...

Hi Joerg

See if this helps:

http://www.advancedinstaller.com/user-g ... iexec.html

The /x flag is used to uninstall. You can use the GUID or MSI name to uninstall.

Regards, Hamad

Just so this doesn't get lost in translation, can you elaborate on what the array looks like in this case i.e. how many elements, what is the data type etc.

By storing the image into the database, it becomes easier to manage the data as a single entity. However, you need to consider the volume and disk space requirements too, as images can easily take up a lot of space over time. Perhaps you can cleanse the database of old records by archiving them into ...

Please check what tables in your database are the biggest i.e. take up the most space. I suspect the 10GB space is not taken up by your LANSA source code, but rather by other things that may be expendable.

Perhaps you can take a look at tinyurl too:

http://tinyurl.com/

Does the job quite simply.

You just need to make sure that you set the library list for the actual job that you are using.
i.e. setting the *LIBL for a different job will obviously not help the server module execution.
You have already verified that CALL works fine, you could also test the use of EXEC_OS400.

I would agree with Stewart on this one. There is little gained by mixing up the two executions and such implementations can easily become maintenance nightmares for new developers who inherit the application code. Especially since all the LANSA training and examples follow a clean path as far as ...

This is well documented by IBM and LANSA too.

Has to be set up on the IBM i server first by testing that IBM Client Access (or any other emulator that supports SSO) works well. Then review LANSA documentation e.g.

http://docs.lansa.com/14/en/lansa011/index.htm#lansa/l4wadm02_0225.htm ...

Hi Art, it looks like you need to have two VL installations on your machine, if you want to work in two partitions as the same time.

Looking at the things that can potentially bypass debugging in an IDE session, I came across some interesting findings that I hope will help other Visual LANSA developers too. Lets start by a short introduction to how debug works in Visual LANSA.

When you start executing a component in your VL IDE ...

This seems to work for a VL Grid.
#STD_BIN is a binary field.

Evtroutine Handling(#com_owner.Initialize)
Set Com(#com_owner) Caption(*component_desc)
Use Builtin(HEXTOBIN) With_Args('0D') To_Get(#STD_BIN)
#GridColumn1.caption := 'This is' + #std_bin.AsString + 'a Test'
Endroutine

SELECT_SQL is faster as it bypasses LANSA OAM's and gets direct access to the SQL table via the configured ODBC driver.

Converting from an IBMi server to a Windows SQL Server is a non-trivial exercise. You have to cater for platform specific coding as well as things like application performance ...

Just before your Add_Entry line, where you add your entry into your list, you can accumulate your total e.g.

#TotalField := #TotalField + #NumFieldFromList

After you are done populating the list, your #TotalField will contain the sum of all #NumFieldFromList entries.
Don't forget to reset ...

It looks like sliding the UAC slider bar to the bottom is no longer enough. You now need to make a Registry change too:

In the Windows registry (regedit.exe), locate :
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\policies\system

Find the node "EnableLUA" and set it's value to a ...

See if you can get two more CPU cores added to your VM. That will also enhance the IDE performance, especially when you are checking in/out and compiling things.