My IT department are encouraging me to have a look at the new Sharepoint (subtext: we would like you to use this instead of DB/Textworks). I'm just wondering if anyone has had an opportunity to review Sharepoint's functionality against DB/Textworks.
DB/Text is a Database Management tool, Sharepoint is not. DB/Text can essentially do anything, including plugging in" to sharepoint. What I am saying is that DB/Text "can do" a lot more "things", while sharepoint is a lot more "restricted." However DB/Text/WPP comes with hardly any of the functionality out of the box, if you want features akin to sharepoint you have to develop them, or take a look at Presto (http://www.inmagic.com/products/research/presto.html)
Essentially you cannot make an apples to apples comparison.
Luke Stephenson
Posts: 112 | Location: Ottawa, Ont, Canada | Registered: Sun July 13 2003
We also have our InMagic content indexed in the SharePoint 2007 search engine and it is coming up fine via a Business Data Catalog (BDC) connection. That said, it does require a constant audit to ensure that changes (new items or deletions in your InMagic databases) get reflected in the SharePoint search engine.
Your IT department is likely looking at the list functionality in SharePoint as a possible replacement for InMagic. This may be the case for simple databases with few fields but a list is not an application and it does not match the functionality of say an online public access catalogue which does more than simply return a list of items to users.
