mikelandl

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!

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!

Does anybody know if there is an easy way to align static text in the Open Client?

For example, we have a screen with the following static text:

Heading 1            :

Heading    2         :

The third heading:

We would like the colons to line up as they do above (and they do in the MFC client) but in the Open Client they display as:

Heading 1 :

Heading    2 :

The third heading:

I believe the Open Client uses proportional fonts (namely Arial) as a default font for static text so I overwote the static text CSS to use monospace but that didn't really help at all. The alignment of the static text is set to 'default'. I've tried other options (i.e. mono, both, fill, etc) but none of them help.

Thanks.

We've started testing out the Open Client and have run into a few issues, one of which is the date picker.

At the moment all of our date fields are combo boxes which we attach a calendar icon to (we use a combo box so we can display the calendar icon inside of the combo box). In 'on window' of the combo box we call a window function that wraps an ActiveX control to display a calendar.

ActiveX doesn't work in Open Client so we would like to use the date picker but we would still like to have things work the way they current do if the user is using the MFC client. It seems like the date picker only works if the field is an edit box, not a combo box.

Does anybody know if the Open Client date picker can work with a combo box?

Thanks.

How do you guys handle record locking when it comes to ProIV and a database? 

We're currently running in ProIsam but are working towards moving to Postgres.

With ProIsam, if I have a paging screen with a file in add/change/delete mode and lock a record, a second session will not be able to edit that record (obviously) until the first session is finished with it. What I am noticing in our Postgres environment is, in the same scenario, the record stays locked until the first session exits the paging cycle, which isn't ideal for us. In the Postgres environment I've added the commit() statement in after write of the file and now it behaves the same as the ProIsam environment, which is what we want. The ProIV documentation, however, states "It is recommended practice to structure application functions around the automatic commits and to use the COMMIT() statement only when necessary". What do you guys do? 

This is a very simple example. We have other functions that call many other functions which call many other functions, etc. many levels deep. What do you guys do in those scenarios? Ideally we would like to avoid restructuring our functions as much possible. That may result in orphan records being produced but that would be no different than what we have now. Not ideal but it is reality at the moment.

Thanks.