Splitting db - Convert or not?

[WrHn85]

Hi, hope someone here has experience with this issue.

Our system was recently converted to much tighter secured network environment and moved to Office 2003 (still Windows XP).

Within the next couple of weeks we expect to split/secure our new db for shared use across a network (approx. 6-8 users at any one time).

I want to keep the db in 2000 as long as possible because I'm doing lots of the work at home and that's what I have. After deployment there will be lots more changes but in managed releases. (sounds official, eh?...)

Does anyone know of any risks I'm running by keeping it in 2000 within Access2003?

Thanks very much,

 

[Banana]

I don't have any experience, but I'd suggest you to grab a list of "What's New" in Access 2003 (surely MSDN or MS has it somewhere on their website) so you know what has been added/enchanced that would not be available in 2000.

HTH.

 

[WrHn85]

Hey, Banana,

Yeah, there's certainly functionoality we will want to take advantage of in 2003. I'm just trying to find out whether we're shooting ourselves in the foot if we stay with Access 2000 db for now (specifically the split/distribute process).

Anybody know something to watch out for?

Thanks

 

[WrHn85]

Cheers, Pat! That's what I was kinda hoping was the case. Thanks.
Kay