Mike Nicholson

Good programmers manage to get a lot done anyway. But often it requires practically an act of rebellion against the organizations that employ them.

Well that bit rang a bell.

And to sum up some of the main reasons we get bad code ...

If I were a cynical man I'd say that you were simply CV gathering here ...

//Mike

If you're that worried ....

http://mycareer.com....?style=enhanced

Looks like Mike does not know everything

Hehe, never claimed to Although linking to an ad from the same company as the original post proves nothing. I posted because (coicidentally, and not because I'm looking at the moment) I've been in touch with both ProIV financials sites in Melbourne - one is recruituiting, but not contractors. The other has just closed a large project and has a surplus of resources so they don't want anybody right now.

Hence my question as to who wanted contractors...

Hi All,


Thanks for the great response on this one. didn't know there were so many ProIV people out there. These roles are now filled however I will be having another drive in a month or so. I will post another update then,


Cheers


Bill

Hi Bill

Perhaps now that the post has been filled you could tell us who this was. I'm interested as I've been in touch with both large ProIV financials sites in Melbourne in the last week and neither of them are taking contractors (although one is taking full-time staff).

If I were a cynical man I'd say that you were simply CV gathering here ...

//Mike

I was editing a function in VIP and got bounced off of our server. When I try to gain access to that function again it says that the function is locked by another session and will only let me have it in 'lookup' mode. I have restarted ProIV via service manager but still can't get to it. Does anyone have any ideas how to regain access.

thanks
chuckl

It's probably your old session locking it. Check if the session is active - if it is then kill it. If not then just wait a little while for the locks to be cleared and you should be fine.

I think you'll find that Sort/Select logic is a filter that is applied before control is passed to the user to select. So it is active before the user selects anything rather than when they do the selection.

I think that the Before Write logic will get hit even though you can't do a DSELF at that point you might be able to do other things.

Yep to both I was hoping for a way to actually identify the records that had been selected. Resorted to LSEXITING and looping back in the end, although it's not an ideal solution.