Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
ODBC / Re: Operator error
« on: February 27, 2023, 09:35:52 PM »
Well, while hunting I found this syntax that worked for my query.
WHERE SO_SalesOrderDetail.ItemCode='S-205180' AND SO_SalesOrderHeader.OrderDate> {d'2022-06-01'}
The {d'2022-06-01'} solved this problem.
WHERE SO_SalesOrderDetail.ItemCode='S-205180' AND SO_SalesOrderHeader.OrderDate> {d'2022-06-01'}
The {d'2022-06-01'} solved this problem.
2
ODBC / Operator error
« on: February 27, 2023, 09:16:59 PM »
Select tbl.column, tbl.column....
FROM tbl
WHERE SO_SalesOrderHeader.OrderDate>'2023/01/28'
attempting to get records > than '2023'01'28' below error
[ProvideX][ODBC Driver]Invalid operand for operator: >
Is there a syntax here I'm missing?
Very best regards,
Bret
FROM tbl
WHERE SO_SalesOrderHeader.OrderDate>'2023/01/28'
attempting to get records > than '2023'01'28' below error
[ProvideX][ODBC Driver]Invalid operand for operator: >
Is there a syntax here I'm missing?
Very best regards,
Bret
3
ODBC / DATE field query
« on: February 27, 2023, 07:52:24 PM »
Using a select against a table column in DATE FORMAT.
SO_SalesOrderHeader.OrderDate
returns this 9/30/2020 12:00:00 AM
Any way to format the return value as? 9/30/2020
I have the ODBC manual, but can't figure it out.
Thanks
SO_SalesOrderHeader.OrderDate
returns this 9/30/2020 12:00:00 AM
Any way to format the return value as? 9/30/2020
I have the ODBC manual, but can't figure it out.
Thanks
4
ODBC / Powershel ODBC query Lexical identifier error
« on: October 02, 2021, 02:10:07 PM »
I'm writing a powershell script to run the following query, but I get the lexical identifier error.
Original SQL script:
SELECT SO_SalesOrderDetail.SalesOrderNo, SO_SalesOrderHeader.OrderType, SO_SalesOrderHeader.OrderStatus, SO_SalesOrderDetail.LineKey, SO_SalesOrderDetail.ItemCode, SO_SalesOrderDetail.ItemCodeDesc, SO_SalesOrderDetail.PromiseDate, SO_SalesOrderDetail.PurchaseOrderNo, IM_ItemWarehouse.QuantityOnHand, IM_ItemWarehouse.QuantityOnPurchaseOrder, IM_ItemWarehouse.QuantityOnSalesOrder, IM_ItemWarehouse.WarehouseCode, IM_ItemWarehouse.BinLocation
FROM (SO_SalesOrderDetail INNER JOIN SO_SalesOrderHeader ON SO_SalesOrderDetail.SalesOrderNo = SO_SalesOrderHeader.SalesOrderNo) INNER JOIN IM_ItemWarehouse ON SO_SalesOrderDetail.ItemCode = IM_ItemWarehouse.ItemCode
WHERE (((SO_SalesOrderDetail.ItemCode)="S-209220"));
My attempt at adding the lexical correct version using oj:
"SELECT SO_SalesOrderDetail.SalesOrderNo, SO_SalesOrderHeader.OrderType, SO_SalesOrderHeader.OrderStatus, SO_SalesOrderDetail.LineKey, SO_SalesOrderDetail.ItemCode, SO_SalesOrderDetail.ItemCodeDesc, SO_SalesOrderDetail.PromiseDate,
SO_SalesOrderDetail.PurchaseOrderNo, IM_ItemWarehouse.QuantityOnHand, IM_ItemWarehouse.QuantityOnPurchaseOrder, IM_ItemWarehouse.QuantityOnSalesOrder, IM_ItemWarehouse.WarehouseCode, IM_ItemWarehouse.BinLocation
FROM (SO_SalesOrderDetail {oj SO_SalesOrderHeader ON SO_SalesOrderDetail.SalesOrderNo = SO_SalesOrderHeader.SalesOrderNo)} {oj LEFT INNER JOIN IM_ItemWarehouse ON SO_SalesOrderDetail.ItemCode = IM_ItemWarehouse.ItemCode}
WHERE (((SO_SalesOrderDetail.ItemCode)='S-209220'));"
Best regards
Original SQL script:
SELECT SO_SalesOrderDetail.SalesOrderNo, SO_SalesOrderHeader.OrderType, SO_SalesOrderHeader.OrderStatus, SO_SalesOrderDetail.LineKey, SO_SalesOrderDetail.ItemCode, SO_SalesOrderDetail.ItemCodeDesc, SO_SalesOrderDetail.PromiseDate, SO_SalesOrderDetail.PurchaseOrderNo, IM_ItemWarehouse.QuantityOnHand, IM_ItemWarehouse.QuantityOnPurchaseOrder, IM_ItemWarehouse.QuantityOnSalesOrder, IM_ItemWarehouse.WarehouseCode, IM_ItemWarehouse.BinLocation
FROM (SO_SalesOrderDetail INNER JOIN SO_SalesOrderHeader ON SO_SalesOrderDetail.SalesOrderNo = SO_SalesOrderHeader.SalesOrderNo) INNER JOIN IM_ItemWarehouse ON SO_SalesOrderDetail.ItemCode = IM_ItemWarehouse.ItemCode
WHERE (((SO_SalesOrderDetail.ItemCode)="S-209220"));
My attempt at adding the lexical correct version using oj:
"SELECT SO_SalesOrderDetail.SalesOrderNo, SO_SalesOrderHeader.OrderType, SO_SalesOrderHeader.OrderStatus, SO_SalesOrderDetail.LineKey, SO_SalesOrderDetail.ItemCode, SO_SalesOrderDetail.ItemCodeDesc, SO_SalesOrderDetail.PromiseDate,
SO_SalesOrderDetail.PurchaseOrderNo, IM_ItemWarehouse.QuantityOnHand, IM_ItemWarehouse.QuantityOnPurchaseOrder, IM_ItemWarehouse.QuantityOnSalesOrder, IM_ItemWarehouse.WarehouseCode, IM_ItemWarehouse.BinLocation
FROM (SO_SalesOrderDetail {oj SO_SalesOrderHeader ON SO_SalesOrderDetail.SalesOrderNo = SO_SalesOrderHeader.SalesOrderNo)} {oj LEFT INNER JOIN IM_ItemWarehouse ON SO_SalesOrderDetail.ItemCode = IM_ItemWarehouse.ItemCode}
WHERE (((SO_SalesOrderDetail.ItemCode)='S-209220'));"
Best regards
5
ODBC / Sage/ProvideX ODBC
« on: December 09, 2020, 05:38:53 PM »
We use Sage 100 which uses a ProvideX backend DB running on a virtual 2012 server VM
Clients tested Windows 10 64, Windows 7 64
We access Sage 100 using the SOTOMAS ODBC driver
Under Lazarus/Delphi pascal program
Here's the problem.
When a Sage 100 client is running on a client machine, we have a 4 second delay before an ODBC connection completes.
When a Sage 100 client is NOT running on a client machine, we have a 1 second ODBC connection time.
Access can make the connection in 1 second regardless of the Sage client running or not.
Any ideas why?
Clients tested Windows 10 64, Windows 7 64
We access Sage 100 using the SOTOMAS ODBC driver
Under Lazarus/Delphi pascal program
Here's the problem.
When a Sage 100 client is running on a client machine, we have a 4 second delay before an ODBC connection completes.
When a Sage 100 client is NOT running on a client machine, we have a 1 second ODBC connection time.
Access can make the connection in 1 second regardless of the Sage client running or not.
Any ideas why?
Pages: [1]