Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Access to flowfields via ODBC / Access
Christian_Buehl
Member Posts: 145
I'm a little bit confused now :roll: while I tried the following:
With MS-Access and the ODBC driver I tried to access a flowfield as described in the C/ODBC guide. I tried to enter this sql-command in MS-Access:
The result is the net_change but it seems that the flowfilter was not set (as should be). After some tests I tried to use msquery32 with the exactly same sql-statement. I was lucky because it worked right and the filter was correctly used.
Does anyone know the reason for this strange behaviour?
Is there any setting for MS-Access to make the filter happen?
(I'm using the native database in version 3.70.A with corresponding ODBC-Driver and Access XP)
With MS-Access and the ODBC driver I tried to access a flowfield as described in the C/ODBC guide. I tried to enter this sql-command in MS-Access:
SELECT No_, Name, Net_Change FROM G_L_Account WHERE Date_Filter='010404..300404';
The result is the net_change but it seems that the flowfilter was not set (as should be). After some tests I tried to use msquery32 with the exactly same sql-statement. I was lucky because it worked right and the filter was correctly used.
Does anyone know the reason for this strange behaviour?
Is there any setting for MS-Access to make the filter happen?
(I'm using the native database in version 3.70.A with corresponding ODBC-Driver and Access XP)
0