Jump to content

Dan Shreeve

Member Since 02 Apr 2003
Offline Last Active May 10 2012 04:49 PM

Posts I've Made


09 November 2009 - 02:02 PM

CAVEAT: I have no SQL/Server experience... but..

The error message seems pretty exemplary to be fair. PROIV is presumably trying to lock records in a way that SQL/Server simply does not support when accessing remote tables (ie. tables in another SQL/Server database or instance whatever the appropriate terminology is). It's not necessarily any kind of bug it may really, legitimately not be supported.

You're not telling us very much about the context, even the type of PROIV function in which you're doing this. If I was to make a wild-assed guess I'd say I probably would not expect PROIV to provoke this problem with a report or update but it might within a paging screen in C or D mode?

If the use of the remote table is essential to your problem (ie. you can't change that aspect of things), can you play with the function maybe and see if the problem relates to specific modes and if, say, it's change mode try updating the file in another way than, say. as the primary file in a paging screen?

I asked my question to pro-4 directly as well... They indicated that pro-4 doesn't support accessing remote tables.... My point would be that since it is a query it shouldn't have been locking anything. The error I am receiving is due to what ever other code they wrap around my sql. Which from the error it sounds like they were using a cursor which I am not even sure was necessary.

In Topic: send xml from pro-iv to a web service

21 May 2009 - 02:35 PM

Please ignore my bad spelling.... should read e-prescription

In Topic: send xml from pro-iv to a web service

21 May 2009 - 01:42 PM

Anyone know how to send xml from pro-iv to a web service running in a third party application on the client machine. I am working on some pro-iv functions that need to interact with an e-proscription software via the web service.

Running pro-iv ver 5.5 with SQL server

One way would be for the external app to issue a bus&task call (p4gateway) to run an xml report - that can output along the bus. But you might want to read the p4 documentation on the subject as you may be able to use p4 web services.

The communication would be initiated from the pro-iv side. For example to start the e-proscription sofware, set the current user, and select a specific patient in the e-prosciption software when I press a button in my pro-iv function to proscribe medication.

To select the current patient the following xml needs to be presented to the webservice:





In Topic: Ver 6 Documentation

18 September 2006 - 05:38 PM

I had the same problem. However, once I installed version 6, the docs that get installed with version 6, worked fine.

In Topic: Webclient 3 Dropping screen elements

16 May 2005 - 08:52 PM

I went and double checked and sure enough I had not specified gui heigth and width for the images... But even after doing so the screen still came up the looking the same way.