2.6 standard DB migration into SQL DB

pciccone
Member Posts: 14
During a test run of a SQL upgrade of our Navision 2.6 product we encountered some bad dates (expressed as 01/01/0025, etc). We have come to learn (from reading these forums) that this has happened to several other users as well.
In response to this problem a codeunit 104015 was developed contained within the migrate.fob to find the problems and create a new codeunit to repair them all aimed at allowing an error-free SQL migration.
I was very excited to read that we can repair these problems with this code since we don't own a developers license. However, when I attempted to run the codeunit after compiling it we received a "You don't have permisisons to run this object" message (even under a SUPER role account).
I don't know if I have provided enough information for someone to help us, but is their any reason we should / could not run the migrate.fob's codeunit to analyze our database tables?
Sadly, our solution provider does not even know what this migrate.fob is, or even heard of the "upgtk" upgrade toolkit. All they continue to do is offer "support on a billable basis" or "run under the direction of a Certified Navision Developer. You are possibly messing with the integrity of your FASB and GAAP compliant Accounting Data."
I appreicate your time in reading my cry for help.
In response to this problem a codeunit 104015 was developed contained within the migrate.fob to find the problems and create a new codeunit to repair them all aimed at allowing an error-free SQL migration.
I was very excited to read that we can repair these problems with this code since we don't own a developers license. However, when I attempted to run the codeunit after compiling it we received a "You don't have permisisons to run this object" message (even under a SUPER role account).
I don't know if I have provided enough information for someone to help us, but is their any reason we should / could not run the migrate.fob's codeunit to analyze our database tables?
Sadly, our solution provider does not even know what this migrate.fob is, or even heard of the "upgtk" upgrade toolkit. All they continue to do is offer "support on a billable basis" or "run under the direction of a Certified Navision Developer. You are possibly messing with the integrity of your FASB and GAAP compliant Accounting Data."
I appreicate your time in reading my cry for help.
0
Comments
-
The objects contained in migrate.fob require a developer license to run. If your NSC is unfamiliar with the SQL upgrade process perhaps they can assist you in finding another NSC to assist. Another option would be to acquire the solution developer granules (expensive). Either way, I would expect to incur some expense. (This is not a hobby).There are no bugs - only undocumented features.0
-
Can you recommend any solution developers that might be able to assist in an area such as this? Remote access into our systems is easily accomplished so geographic location is not a problem.
Cost is the biggest problem for me as I have no money in the IT budget right now for this yet I need to get it done. I know a miracle0
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
- 1.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