Thank you all for your help
And nothing worked better then dear old cast.
I would still like to understand better the decimal date type multiplying rules. If there's any good article you'd like to share please post below. thank you all.
hilaDG
Last Activity: Jun 17 '10, 04:00 AM
Joined: Apr 23 '10
Location:
-
Yes, I guess I'll have to settle with a CAST
But if you know of anything in the database definitions that could cause this change, please let me know. Thanks for your help.Leave a comment:
-
No, it didn't
(and it played with isnull(), just to be sure that it doesn't matter...)
The reason I need this in the first place is that Access sees a Deciaml (38, 5) and reads it as text.Leave a comment:
-
My Float had become Decimal (38, 5)
Hi All,
I have a query that refers to a value in a table that is stored as a float like this:
And the SSMA tells me that this view had po_account (INT), po_quantity...Code:VIEW [dbo].[v_cash_sub] AS SELECT po_account, SUM(po_quantity ) as cash FROM dbo.position INNER JOIN dbo.security ON se_id = po_security WHERE se_cash <> 0 GROUP BY po_account
-
If you don't have a column defined access would never define one for you. It could be so many things other then a column: a form, a text box, a query, that access simply cannot assume a column. So if you want one you'll have to define it by yourself....Leave a comment:
-
Why not simply link the table from SQL to access?
from my experience, SQL handles all those CASE.. WHEN way more gracefully then MS-access.
Create an ODBC server, and go to the tables and use link tables in order to link to that SQL server. This way you don't have to re-create the entire table definitions, etc, with MS-AccessLeave a comment:
No activity results to display
Leave a comment: