Visual LANSA Forum

I would make the edit field have zero decimals, editcode Z. Then just divide it and put it in the display field. You can use the keypress event to keep them in sync.

I don't have an answer for you, but we had terrible speeds when saving images to IBM i.

I had to rewrite the app in VL-WIN and deploy it.

alphabeta13 wrote: ↑

Tue Mar 24, 2020 10:41 pm

Thank you all for your responses.

I have reached out to Lansa and was advised to close the task and then check the objects out using a new task.
It worked.

Regards,
Taufik

Sounds familiar

That didn’t work for me so I went nuclear

Sounds like OP is a one man shop as long as everything is checked in go crazy!

If you are sure that the other user checked in all of his changes, I would close that task and create a new one. In green screen housekeeping, work with tasks, just change the status of the task to CLS, press enter, then FIN. Create another task, and refresh your PC tasks and then use that new task ...

alphabeta13 wrote: ↑

Sat Mar 21, 2020 7:14 am

I tried checking it out as read-only, compiled the object successfully, but then receiving the same messages when checking it back in.

Any ideas on how to resolve or get around these messages?

Regards,
Taufik

If you checked it out as read only you don't need to/can't check it in.

I know you said user that starts job is *ALLOBJ but you might want to check to see if the user is authorized to the parent directories.

I used Regedit to remove Word activex entries for older versions. In fact I deleted all of them and then did a repair in programs and features. This solved my problem.

I did another install of LANSA and pointed it to the existing database from my old laptop. I can quick export what I need.

My ODBC data source originally pointed to default database A4DDS. I changed it to V14SP2. To make sure it was using new database, I renamed A4DDS to A4DDS_X.

IDE won't start, there must be another setting somewhere.

I have a new installation of V14SP2 on a new laptop. I have the .MDF and .LDF files from the old laptop. I'd like to temporarily point my IDE to the other DB so that I can quick export a few missing components (they weren't checked in to repository on IBM i) I changed my ODBC source default database...

I don't have that file on my V14 IFS.

We submitted an incident to support in USA. Does anyone think the fact that I click one activex that after selecting it shows a different type lib id could be an IDE problem?

Several users had upgraded to Office 2019 and this problem started. So we put DEV and all PC's on Office 2016 so they all match.

Something is wrong when I select the Activex the typelibid doesn't show what I double clicked on.

Need to revisit this :oops: Here is what my DEV pc shows when I'm trying to select the Word activex component. Notice the "FF" in the type id. shot1.png When I click on the typelib ID to add that, I go to the microsoft word component, select it and it brings in a different typelibid. The FF is what ...

Ok I see. Thanks

Hi David: I don't know the answer but I was wondering what you were doing with the after_read trigger? Anything interesting related to the blob?

I did a new installation into the same directory, and it looks like it's going. Installing EPC's now.

Thanks James. The logs pointed to a corrupt vlfruntime.zip. I fixed that file and now it says install is finished and it was going to start LANSA to initialize the DB. The LANSA icon on my desktop says target not found. I tried to repair the installation and when select the installation and click ne...

Trying to do install on new laptop. Seeing this error, retries didn't help. Will submit a support incident tomorrow, also trying google but nothing yet. Any ideas?