PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: [1] 2 3 ... 10
1
ODBC / Re: Join Tables Error Identifier
« Last post by Devon Austen on June 11, 2021, 02:15:23 PM »
Are the table names all correct and is that the correct field names?

If you do it without the WHERE clause to test does it work?
2
ODBC / Re: Join Tables Error Identifier
« Last post by eldonfsr on June 11, 2021, 12:46:14 PM »
select *   from  {  oj   PO1_PurchaseOrderEntryHeader  INNER  JOIN PO2_PurchaseOrderEntryLine ON PO1_PurchaseOrderEntryHeader.PurchaseOrderNumber = PO2_PurchaseOrderEntryLine.PurchaseOrderNumber }  WHERE  PO1_PurchaseOrderEntryHeader.PurchaseOrderDate =  {d"2015-08-05"}

even i write without # is the same message...
 
3
ODBC / Re: Join Tables Error Identifier
« Last post by Devon Austen on June 11, 2021, 12:39:49 PM »
Is the # symbol part of the table name?

If it is not then it likely is the problem as that is not supported syntax.

If it is part of the table name then it looks like it is missing from the WHERE clause.
4
ODBC / Join Tables Error Identifier
« Last post by eldonfsr on June 11, 2021, 11:17:48 AM »
I have this SQL statements but when is executed send a error not found indentifier

select PurchaseOrderNumber, PurchaseOrderDate, Vendorname, ItemNumber  from  {  oj   #PO1_PurchaseOrderEntryHeader  INNER  JOIN #PO2_PurchaseOrderEntryLine ON #PO1_PurchaseOrderEntryHeader.PurchaseOrderNumber = #PO2_PurchaseOrderEntryLine.PurchaseOrderNumber }  WHERE  PO1_PurchaseOrderEntryHeader.PurchaseOrderDate =  {d"2015-08-05"}

what i doing wrong...
5
Language / Re: schedule a providex program
« Last post by Mike King on June 10, 2021, 11:32:11 AM »
Assuming you are using a properly registered license there should not be any prompting for an OK by PxPlus / ProvideX.  The EXE initialization only prompts for an OK to confirm an issue with the license such as running on a temporary key used for software installation which has an expiry date that you need to confirm.

I myself have the Windows Task Scheduler run a couple of PxPlus programs every night with no problem.
6
Language / Re: Intermittent error 261 and 278
« Last post by Dave Fullerton on June 10, 2021, 11:30:17 AM »
Hi Mike:

Thanks for the link - I will pass it on.  I had mentioned to their IT support that this might be a reason, but they didn't know anything about the setting.   I checked the status of the drives in File Explorer, and did not see the red X that usually indicates the disabled drive, and the drive was being used pretty regularly (or so I'm told), but hopefully this link will remove that issue from the equation.

Dave
7
Language / Re: Intermittent error 261 and 278
« Last post by Mike King on June 10, 2021, 11:25:08 AM »
Dave

Make sure they have disable the Windows idle timeout on the mapped drives.  What can happen with mapped drives is if there is no activity for an extended period of time the OS drops the connection which then causes trouble when we try to do subsequent IO.

Here is a link that lets you know how to change the timeout setting:

https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drive-connection-to-network-share-lost
8
Language / Re: Intermittent error 261 and 278
« Last post by Dave Fullerton on June 10, 2021, 09:39:08 AM »
Hi Devon:

The problem is, that the errors seem to happen in *winproc, where I don't have a lot of control, and one of them wasn't associated with a Read.  I could suggest moving to client/server, but they will be winding down use of our application in the next seven months, so that really isn't an option.  As far as retries are concerned, I have tried going back to the statement to re-execute it, without success. 

Before this server change, the application was running quite well for over a decade without issue.

Thanks for the input - I am hoping that their tweaks (which seem to take an inordinate amount of time) will work.  If not, I may need to get them to go to WindX.

Dave
9
Language / Re: Intermittent error 261 and 278
« Last post by Devon Austen on June 10, 2021, 08:53:42 AM »
I would agree with you and I also suspect a networking issue.

Using mapped drives is always risky in your application because there is no fault tolerance in the protocol really. If there is any networking issue while accessing/modifying data on a mapped drive it will likely result in a error or possible data loss or corruption. That is why we developed the PxServer product to allow more reliable and secure remote data access.

Now I am guessing you don't really have an option here and mapped drives must be used. In that case the best you can do is make the network as reliable as it can be made. Unfortunately I can't really help you there as I am not an expert in VM networking.

You also want to make sure the program can handle the errors when they do happen by for example retrying the read. This would allow a blip in the network to not cause an error it would just try again and it would likely succeed. Now you would probably have to add error handling like that around all mapped drive file IO to make it really reliable. This obviously may be a big change which is not really possible given this customer had a working system until the server change.
10
Thin Client/WindX / Re: Start_up for a spawned windx session
« Last post by Dave Fullerton on June 09, 2021, 06:04:35 PM »
Hi John:

We use this in our menu to spawn new sessions

4145 call "*windx.utl;spawn",quo+local_dir$+"parms"+fid(0)+".txt"+quo,"",fid(0)

The txt file is treated as a program.

Hope this helps.

Regards

Dave Fullerton
Pages: [1] 2 3 ... 10