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
ADO Library
tullio
Member Posts: 39
I have Navision 5.0 SP1 DB.
There are some CODEUNIT that using ADO Library and RUN with NAS.
Nas PC was windows 2003 server. All work great.
To develop we are using DB copy installed on windows 2008 server with same NAV version client/server.
I change two codeunit without change ADO reference but, when I import from test new object version start problem.
System show this error:
"It is not possible to assign a _Parameter to a Parameter"
stopping on an instruction that was not not modified!!!
I roll back old codeunit but now error stop in other codeunit that was called from that I changed and restored.
Investigating more I realize that the codeunti called by that was modified have changed in size. Their size is increased (some fate and time!!!).
Restoring also this all work great.
So, importing objects compiled with other libraries version (I suppose) something has not worked and has also modified codeunit connected!!!!!!
Now after a long time spent to understand the problem, I realized that the libraries mentioned are the same (ADO 2.7) version but in a develop environment is oldest.
In the test PC under regedit key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version is 6.1.7600.16385while on the other version was 6.1.7601.17514
So develop PC library version are earlier .... !!!
Finally exporting same object codeunit from different DB (develop DB and current DB) when I compare them using winmerge all reference row to ADO libray was modified and appear different in the develop version.
Develop version:
EVENT vRecordSet@1000000007::WillChangeField@9(cFields@1000000003 : Integer;Fields@1000000002 : Variant;adStatus@1000000001 : Integer;pRecordset@1000000000 : Automation "{EF53050B-882E-4776-B643-EDA472E8E3F2} 2.7:{00000556-0000-0010-8000-00AA006D2EA4}:'Microsoft ActiveX Data Objects 2.7 Library'._Recordset");
Current DB
EVENT vRecordSet@1000000007::WillChangeField@9(cFields@1000000003 : Integer;Fields@1000000002 : Variant;adStatus@1000000001 : Integer;pRecordset@1000000000 : Automation "{EF53050B-882E-4776-B643-EDA472E8E3F2} 2.7:{00000556-0000-0010-8000-00AA006D2EA4}:'Microsoft ActiveX Data Objects 2.7 Library'._Recordset_Deprecated");
How I can solve this problem?
Someone can help me to understand and solve problem?
Why same code not work and show strange error??
There are some CODEUNIT that using ADO Library and RUN with NAS.
Nas PC was windows 2003 server. All work great.
To develop we are using DB copy installed on windows 2008 server with same NAV version client/server.
I change two codeunit without change ADO reference but, when I import from test new object version start problem.
System show this error:
"It is not possible to assign a _Parameter to a Parameter"
stopping on an instruction that was not not modified!!!
I roll back old codeunit but now error stop in other codeunit that was called from that I changed and restored.
Investigating more I realize that the codeunti called by that was modified have changed in size. Their size is increased (some fate and time!!!).
Restoring also this all work great.
So, importing objects compiled with other libraries version (I suppose) something has not worked and has also modified codeunit connected!!!!!!
Now after a long time spent to understand the problem, I realized that the libraries mentioned are the same (ADO 2.7) version but in a develop environment is oldest.
In the test PC under regedit key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version is 6.1.7600.16385while on the other version was 6.1.7601.17514
So develop PC library version are earlier .... !!!
Finally exporting same object codeunit from different DB (develop DB and current DB) when I compare them using winmerge all reference row to ADO libray was modified and appear different in the develop version.
Develop version:
EVENT vRecordSet@1000000007::WillChangeField@9(cFields@1000000003 : Integer;Fields@1000000002 : Variant;adStatus@1000000001 : Integer;pRecordset@1000000000 : Automation "{EF53050B-882E-4776-B643-EDA472E8E3F2} 2.7:{00000556-0000-0010-8000-00AA006D2EA4}:'Microsoft ActiveX Data Objects 2.7 Library'._Recordset");
Current DB
EVENT vRecordSet@1000000007::WillChangeField@9(cFields@1000000003 : Integer;Fields@1000000002 : Variant;adStatus@1000000001 : Integer;pRecordset@1000000000 : Automation "{EF53050B-882E-4776-B643-EDA472E8E3F2} 2.7:{00000556-0000-0010-8000-00AA006D2EA4}:'Microsoft ActiveX Data Objects 2.7 Library'._Recordset_Deprecated");
How I can solve this problem?
Someone can help me to understand and solve problem?
Why same code not work and show strange error??
0