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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
XML and NAS
Toady
Member Posts: 3
I am trying to read an xml file from message Queues and populate a couple of holding tables using NAS.
I have run the routine picking up an xml file off the c:\ and importing and it is fine. When I use Nas and the msg queues I get an error when trying to run XMLDOM.Getelementsbytagname. The event viewer message is
'This automation variable has not been instantiated. You can instantiate it by either creating or assigning it.'
I have managed to identify this as the cause but cannot identify what the fix is.
Has anyone had a similar problem or can someone provide an insight.
I wondered if it was case sensitive but I have managed to read the file if it is on my c:\ and I call the routine via a report.
Thanks
Chris
I have run the routine picking up an xml file off the c:\ and importing and it is fine. When I use Nas and the msg queues I get an error when trying to run XMLDOM.Getelementsbytagname. The event viewer message is
'This automation variable has not been instantiated. You can instantiate it by either creating or assigning it.'
I have managed to identify this as the cause but cannot identify what the fix is.
Has anyone had a similar problem or can someone provide an insight.
I wondered if it was case sensitive but I have managed to read the file if it is on my c:\ and I call the routine via a report.
Thanks
Chris
0
Comments
RIS Plus, LLC
I have been informed that there is a known problem with vb6 and xml where the xml document is tainted with ? at the start. This means that the document is unable to be read.
I have a colleague looking into a solution for me at the moment.
Cheers Anyway