Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Insert into SQL --> Access
kanika
Member Posts: 247
Hi @ll,
I have a query in access (office professional Plus 2010) and exactly the same query in SQL (Server 2008 R2), if I run it from SQL inserts the data in the table perfectly but if I run it from Access I get the famous "Microsoft Access set 0 fields to Null due to a bug in the type conversion and added 732 records to the table due to key violations, 0 records due to lock violations, and 0 records due to validation rule violations "
I need to know if there is a parameter in the query property to prevent this error, because the code is exactly the same as SQL (I did copy and paste) and SQL works perfectly.
anyway how to run SQL code from Access?
thanks to @ll
I have a query in access (office professional Plus 2010) and exactly the same query in SQL (Server 2008 R2), if I run it from SQL inserts the data in the table perfectly but if I run it from Access I get the famous "Microsoft Access set 0 fields to Null due to a bug in the type conversion and added 732 records to the table due to key violations, 0 records due to lock violations, and 0 records due to validation rule violations "
I need to know if there is a parameter in the query property to prevent this error, because the code is exactly the same as SQL (I did copy and paste) and SQL works perfectly.
anyway how to run SQL code from Access?
thanks to @ll
0