Will Mvbase or D3 run on the Microsoft Windows Small Business Server??

Will have to move, but which way to go??

Blatant ad....

Have you looked at OpenQM? We would gladly help you with any migration
issues.


Martin Phillips, Ladybridge Systems.

D3 will run on SBS

Rodney wrote:

Rodney,

If I remember correctly, you can only run one Small Business Server
in a given domain. It also has to be the Primary Domain Controller.

If you are also running the fax server, Microsoft Exchange, and
Microsoft ISA on SBS, your server might be too busy to support
a very large organization.

Larry Hazel

"Ross Ferris" <rossf (AT) stamina (DOT) com.au> wrote

Personnaly i would go with Unidata - but hey .....

If you don't have SBS 2003 R2 you should. If you got R2 before July
26th you should probably get it again because it had some pre-release
code that shouldn't have been in there. The current re-release should
be OK.

Be sure to allocate a decent piece of hardware to this environment.

<ad>
And if you'd like to integrate your SBS with your D3 or mvBASE DBMS,
let me know. In particular we can integrate your MV app with Exchange
Calendar, Contacts, Journals, etc., get this data from your green
screens, make it available to your GUI's, etc.
</ad>

Tony
TG@ removethisNebula-RnD.com



"Ross Ferris" wrote:

Rodney wrote:
machines alive if you use exchange, but mvBASE does make good use of
whats left of the machine after Exchange has taken it's slice.

Can't say I'd recommend mvBASE or D3 as directions to go for the
future. Try looking at OpenQM or jBASE, both of which should be
reasonably easy to port to. jBASE doesn't like running on SBS too
much - I seem to remember having to "fix" the ports that Exchange uses
so that it didn't interfere with jBASE but I can't remember the details
- might be different with SBS2003R2.

Simon

This isn't really a viable option. If someone is running on D3 or mvBase,
moving to UniData is the last thing anyone should recommend!

If one wants to, however, move to UD then you need some pretty technically
proficient consulting help. :-)

Bill

"Symeon" <symeonb (AT) gmail (DOT) com> wrote

In case anyone doesn't know, Bill has been personally going through
this school of hard knocks for quite a long time now and is thoroughly
versed with these D3 to Unidata concerns. Based on my own experience,
Bill's ongoing adventures, and comments from others who have moved to
Unidata or Universe, I firmly believe that U2 is exclusively a
business decision, not based at all on ease of use or any technical
capabilities. I would prefer a root canal to spending all of my time
with either of the U2 environments. I'm sure many of our colleagues
would disagree.

T

"Bill H" wrote:

I'm really torn in a response to your comments Simon.

As a jBASE Distributor I'd say "YEAH, migrate to jBASE" - and I'll be
happy to help.

As a fan of the D3 platform I will maintain my position that D3 is a
great platform, and if you don't have other over-bearing reasons to
migrate from it then you probably shouldn't.

mvBASE is different - it's a dead-end platform and one of these days
RD just might force mvBASE users to make some sort of decision. If
that time comes then the world is open, D3 is not the obvious
migration choice, and I would strongly encourage people to look at
jBASE.

For the purposes of the OP, mvBASE and D3 should coexist well with
SBS2003. DBMS migration should be done for the right reasons - this
isn't one of them.

T

simon (AT) aphroditeuk (DOT) com wrote: