mibuso.com

I was really working on the basis of this:

David, that's a spot on summary of where i am.. If i hand them a SQL db, knowing NAV structure, they'll pull the few tables and discard the majority of the database... If i give them a few spreadsheets with "the right" information, they'll just use that.

I am (allegedly) the "power user" in our small group... I've written middleware using perl DBI connectors to sync Foxpro data with a MySQL blah blah blah.. but with this C/SIDE Proprietary Navision and little documentation, this group has given me more information than any research i've been able to do.

Hi there,
2.01 is pretty old. With a conversion to SQL I would be carefull and would not recommend doing this for this old version.

As you need to convert your data I would recommend to use dataports for this and export into CSV files.
I remember about using a dataport creator which eased my life pretty much a long time ago.
I found the "Simple Dataport Creator" in the download section, but I'm not sure if this is the same tool I used several years ago.

viewtopic.php?f=7&t=39130

Hope that helps

This is especially true if the client is still using their Navision for something else.

I've cross-posted this to the dynamicsuser.net forums and left this as the summary of what i've heard so far..

The methods of data extraction from a Navision 2.01 native database i am aware of are:

1)running the appropriate tables and copying to Excel
This would work fine but i get "cannot access table" errors on some tables (the "items" table for one) even though i'm a superuser.. can't get past that...


2)Dataports
I'm trying them out now, but getting "you do not have permission" errors when trying to save them, so.. researching what that could be....

3)Conversion
As i understand, tools don't exist outside the Navision Partner network to do this. I have two answers from the two groups:

1)It's easy, pay me and i'll get it done

2)It's very difficult to go from Navision 2.01 -> SQL and you will corrupt data

I'd be thrilled to hire the job out, but I'd like to get a better feel for the cost and caveats of the conversion before before jumping into it. Right now i feel like a little old lady taking her car to the mechanic, they could tell me they need to replace the rings because the brakes squeak, and i'd be none the wiser.

4)From my research.. those are pretty much the range of options, if the group has more, i'd love to hear them.

I'm actually pretty quickly getting over this Navision C/SIDE DB data extraction project learning curve thanks exclusively to the experience i've been able to tap on this group and the mibuso.com forum.. so thanks for that!

If anyone's interested in the job, it sounds like a quick buck... message me.



And like i said over there... thanks for all the valuable insights.. For a small non-profit, a resource like this forum is really invaluable.

Can you see an Item List? This I would consider strange.



What are you saving it as? Try saving it in the 50000+ range
50000
50001
50002
etc.

check you datbase login - you should just have
Role ID : SUPER & SUPER(DATA)

Well there are lots more options. But I think that we are focusing on the ones that makes sense. so my summary...

1/ Open tables and copy to Excel.
Advantages
- You can do it yourself, no NAV skills required.
Disadvantages
- Slow.
- Issues with large tables, might run out of memory
- Permission issues with tables you can't access. (This does seem strange though, you should have permission, it could be that your partner did something with their license).
- Could be problems with delimiters, leading zeros etc in Excel.

2/ Dataports
Advantages
- Dataports only need to be written once.
- You probably have the license to do this.
Disadvantages
- You need to define exactly what is needed, then work with the new company to make sure the Data matches what they need.
- You need some training to learn how to create dataports.
- Its going to take a lot of your time becasue of the learning curve.
- Issues with delimiters commas, quotes etc.

3 / Convert DB to SQL
Advantages
- The new company understand the NAV SQL db, so there is no work involved there.
- You have the SQL DB for ever to use for historical reference.
- You just give it out as a job and everything is converted.

Disadvantages
- Has to be done by someone skilled in NAV and SQL.
- Has to be done twice.

4/ Open DB with 5.00 or later and use the Export To Excel Function.
- Same really as copy paste to Excel, but more "user Friendly"

5/ C/ ODBC
- Similar to Dataports, except your license wont allow this, so a partner needs to do it.

6/ C/FRONT
- Way to complex.

7/ Use report to export data as code.
- Way to complex.

8/ Use Reports to connect via ADO to an external SQL database
- No real advantage over dataports, and more complex.

9/ Move to newer version and export as XML files.
- No real advantage over dataports, and more complex.

So in summary, really its a choice between Dataports and SQL.

In my mind it all comes down to the value of your own time, and how much you will have to pay the CRM company depending on the data type.

If you do the Dataports, you first need to get up to speed. that will probably take you about a day, you will find enough information on MiBuSo and Dynamicsuser.net, to do this. And the tool linked earlier looks like a great start.

Then you need to work with the CRM company to define all the data that needs to be moved over. They may have a list ready that they can give you, in which case its easy. You then need to work out which tables in Navision have the data you need to get, unless they can accept the data in RAW Navision format (which is what everyone here is assuming).

The big thing though is history. Do you need to get any transactional data out? Most likely not, in which case you should be able to do all this your self. But do they need opening balances. If so you need to work out how which flow fields to include and map them to what you need.

but the great thing about Dataports, is that once they are written once its over. You can run them 20 times and not have to do any more work.

With SQL the big plus is that the CRM partner know how to work with the DB, so you just give it to them. But there are two disadvantages,
1/ you need to pay someone to do it,
2/ It needs to be done twice.

In reality it just comes down to the value relation of money vs time. All the other issues are misnomers, since both options give the same end result.

Of course why not simply try to do the dataports yourself, and if that doesn't work, then get someone to convert the database.

Dataports are not difficult, just they are a lot more work then C/ODBC.
From NAV to NAV it is all nice.
Migrating out of NAV is a problem.
Good old Foxpro never dies.
Converting to SQL won't bring anything just slow down.
And you will loose data.
Where are you going to, not NAV again I understand?

The data extraction is the way to extract and to structure data from not structured and semi-structured electronic documents, as found on the web and in various data warehouses. Data extraction is extremely useful for the huge organizations which deal with considerable amounts of data, daily, which must be transformed into significant information and be stored for the use this later on.

For mlre details visit us at
Data Conversion

I found this thread from from the early 2000s. We too have Navision 2. What I am asked is to "extract - capture the Navision email addresses into Excel. The user wants to use the emails for an advertising bulk email project. Is there a process to cultivate the client database into Excel?

Run the customer table and copy and paste to Excel.

I just had a talk with Accounting. Evidently back in 2000 no one in the company anticipated that 'email' would be of use.
Thus when the company customized they did not include email/email report. We can look at individual customers and copy out
the email however to pull out all emails, the email fields, is proving elusive.

Did you try Alex's suggestion. If emails are in the Customer table, then his suggestion should work for you.