Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K 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
- 282 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
How to downgrade an Attain Add-on to Financials 2.60.07
Tommy_Schou
Member Posts: 117
Any ideas?
So far I have found that you can import .fobs from attain 3.01.02 into a Financials 2.60 database but when you try to compile them the runtime crashes.
Changing VAR ID's from @10000000001 to something like @1001 solves some problems but I still get the occasional crash from several objects when I try to compile them and so far haven't been able to identify the reason.
Does anybody know of any tools or guides to help in this process?
So far I have found that you can import .fobs from attain 3.01.02 into a Financials 2.60 database but when you try to compile them the runtime crashes.
Changing VAR ID's from @10000000001 to something like @1001 solves some problems but I still get the occasional crash from several objects when I try to compile them and so far haven't been able to identify the reason.
Does anybody know of any tools or guides to help in this process?
Best regards
Tommy
Tommy
0
Comments
I usualy downgrade via txt files instead of fobs...
How do you go about preparing the objects for downgrading then?
If I export a text-object and import it into Financials and then try to compile it the client runtime simply crashes. No error message. Just a crash.
If I then change all @100000## -no's (id's) in the text file to ie. @10## I can compile it with no trouble. But on some objects the runtime still crashes...
You don't have that problem with ID no's?
Tommy
Downgraded from 3.70 to 2.01 but no problems with the ID's.
Maybe there is some property set that was not there in 2.x
Maybe you can try to export the files from the 2.x database. Sometimes you get some error you can investigate.
You can also try to export from 3.x with text and import to 2.x to see for errors.
Last thing you can try is to open a copy of the 2.x database with 3.x to see if this works.
Sorry, this is all I can thinkabout right now.
Good luck.
Tank you very much. Both for the Good Luck wishes and your effort to assist.
Merry christmas! 8)
Tommy