We are in the process of converting a Filemaker Pro database to Microsoft SQL Server 2000. Does anyone perhaps have any documentation or articles on how to do this?

Thx Mark

Use FM Migrator. But, tell us, why would you want to do this?

Why would you want to migrate from FMP 7 to SQL Server? SQL Server is a lot more stable & more powerful database engine than FMP. FMP is making big improvements but it is still not on the same level as SQL Server. The thing that is holding us back from migrating everything to SQL Server is not having an easy way of putting an application against a SQL Server database. We are looking into using InfoPath to update backend SQL databases to replace some of our FMP applications. If FMP would work as a front-end to SQL that would be awesome! Access does it but is not as easy to work with as FMP is.

Mark, converting the data is no problem. You can export it to a tab file and then DTS it into your SQL tables. It is the actual FMP application that is the hardest to do against SQL. You will need some good applications developers to replicate what you can do in FMP.

Just my opinions,

John

"I disapprove of what you say, but I will defend to the death your right to say it." -Voltaire

-Stanley

What are your reasons for disapproving of what I said?

John

John, i wouldn't say that I disapprove of what you said (though i'd still defend to the death your right to say it ), but i think this

FMP is making big improvements but it is still not on the same level as SQL Server.

is not really a fair comparison. I find it a little bit like saying, "My microwave oven is not on the same level as the electric supply that feeds it."

A lot of people come to this site to unfavorably compare FM to other apps/languages/protocols: "FM is not as good as Access;" "FM is not as good as PHP;" "FM is not as good as C++;" "FM is not as good as whatever else." These comparisons are a little disingenuous because the comparisons are (typically) invalid.

If you're talking about large-scale data hosting that makes data available to a wide range of applications, then absolutely you should choose SQL Server over FM. But good luck developing an interface (a point you alluded to). You sound like you'd be able to, but you're in select company there.

But if you're talking about rapid and simple application development, FM is tons better than SQL Server.

I don't mean to browbeat you on this, because i think you make a great argument in favor of SQL Server as a back end to other apps. I'm just getting weary of people comparing FM to other programs, especially when they compare it to things like scripting languages (which, i know, is not the case here). I guess i chose to discuss it here because, in this case, you were more or less invited to make the comparison, so (hopefully) it won't seem as if i'm flaming you for your comment.

So there.

J

J,

We agree more than you think. I totally agree that for rapid & simple application development, FM is TONS better than SQL Server. FMP has its own niche in the database realm.

Our stand here in our organization is that if the data held in a FMP database reaches a certain level of importance, then it will be migrated to SQL Server & an application will be developed to go against the SQL database.

My post was in response to transpowers comment of why would you want to migrate to SQL Server. I just wanted to throw out some reasons as to why you would want to. I did not take your post as a flame. I was just curious what your thoughts were on this.

So back at ya!

John