Chris Mackenzie

Did you get anywhere with this?  Is it possible to get some extended event monitoring set up on the database?

It is relatively easy to upgrade but there will be problems and you would be well advised to hire an experienced consultant.  There may be several steps - you can't go direct from v4 to v8 - there was a major restructure with v5

Old post but anyway..Long time since i had to do this but you need to check the terminal type in use and ensure the settings are correct - VIp Admin Suite->Toole->Terminal types  - double click a type to open the definition window where system FN keys are defined.  Sometimes a new Type must be created and the exact codes entered in the window by pressing the appropriate fn key.

I looked at ProIV's documentation regarding creating memory files (topic ID 720293) and it has left me more confused than enlightened.

I took the simple approach of changing the file type of one of our existing "working files" and regenning all functions that reference it. It seems to have made no difference at all in execution speed of the report I was testing. The documentation also mentions adding an entry to pro4v7.ini which I did but it still makes no difference. 

Help!

Chaging to mem  file is quite simple - sounds like you did it correctly.  with modern file systems there is a lot of caching going on - if this was a pro-isam or c-isam file originally then converting to mem file may not give as much advantage as you might think - replacing a database table based workfile can give huge performance advantages.  Perhaps theres is something else slowing your report?  What sort of volume of data were you processing using this memory workfile?  I'm quite sure if you really pump up the volume you will see a difference.

what versions - kernel, client & proivDeveloper?