Re: Migrating away from MS-Access

On Sun, 14 Oct 2007 22:39:38 +1000, "John" <nospam@xxxxxxxxxx> wrote:

Confronted with these problems I would first put band-aids on the
existing app in those areas that are used the most. Then I would
redesign the db and work on the new UI and a data conversion program
that copies as much as possible data from old to new db.
If you are unfamiliar with the users needs, you'll need to spend a
fair amount of time analyzing those needs, and getting buy-in from
management for the new design.

-Tom.


Hello there, Im cursing my place of employment...and its taken me a month to
realise it...

The scenario:
Ive just stepped into a role to migrate an access database to VB.Net. The
access database runs on terminal services and supports approximatly 25-30
users. It is crapping out big time, corrupted data, changes to the front end
are difficult for someone unfamiliar with the system (me), the table
structure is bad...really bad....there is a website attached to the backend
aswell...

At some stage we have to migrate the access backend to SQL Server. The
problem is that its all in use and we cannot have downtime.

What approach is best? How can I even fix this dodgy design?

I could just run with it and build dodgyness over dodgyness...fark...haha
god help the next guy if i did that...
I could convince management to hire someone else to develop in parrallel on
both systems so the backend is fixed?
I could develop the new VB.net front end with changes in mind, then fix the
database structure when we migrate
I could migrated access backend to sqlServer backend and continue to use the
Access front end, I very much suspect the front end will fall into a big
pile of crap...

I guess Im not really looking for answers, just venting and curious to see
what other people have delt with...
Thanks for reading!
John

.

Relevant Pages

  • Migrating away from MS-Access
    ... Ive just stepped into a role to migrate an access database to VB.Net. ... At some stage we have to migrate the access backend to SQL Server. ... How can I even fix this dodgy design? ... database structure when we migrate ...
    (comp.databases.ms-access)
  • Re: Migrating away from MS-Access
    ... Ive just stepped into a role to migrate an access database to VB.Net. ... At some stage we have to migrate the access backend to SQL Server. ... A dot-net front end with an MDB file back end is the worst of all worlds. ...
    (comp.databases.ms-access)
  • Re: How to copy current db
    ... You cannot safely copy an Access database while it is in use. ... It also means that the backup itself may be incompatible (e.g. if you copied a table of related records just as someone was deleting a record on the ONE side of the join which then doesn't appear when you copy the primary table.) ... Allen Browne - Microsoft MVP. ... I could close the backend, ...
    (microsoft.public.access.formscoding)
  • Re: backend corrupt
    ... > I have an Access database. ... There are about 6 frontends connecting to ... The frontends are developed in 2000 but run on Access ... The backend is an Access 2000 backend. ...
    (comp.databases.ms-access)
  • Migration to XP
    ... applications with a SQL Server 6.5 backend to Access 2002 ... and our W98 clients to WXP. ... installed and so you cannot print or design reports). ... >databases and other Access database versions we may have ...
    (microsoft.public.access.conversion)