Conversion Access 2000 to 2007

[ggregg]

I have designed many databases using various versions of Microsoft Access. I
now have a need to upgrade to Access 2007. I have just read 1400 page book
on 2007 and have searched microsoft’s web and I still am confused about the
best way to proceed.

I have a client that has a Head Office in one city and a Branch Office in
another city. They want to be able to synchronize databases. I am
considering converting to Access 2007 and using Sharepoint. This client uses
2 of my Access 2000 programs. These 2 programs are very large. They both
link to 122 Tables and have a combined total of approximately 600 Queries,
380 Forms, 280 Reports and over 3,000 Subroutines. Also, Workgroup Security
is essential.

To keep the Security, I need to use SQL Server or Sharepoint. To move the
Database to Sharepoint I have to convert to an accdb. These changes will
require a lot of updates to my programs and changes to the subroutines. One
example is: Sharepoint lists don’t support Referential Integrity and Cascade
deletes which I rely on heavily in the programs. There are many other
examples.

This seems to be a huge undertaking.

I also have another large program in Access 2003 and many smaller ones.
Sometime in the future I’m sure I will have to upgrade to 2007. They don’t
require synchronization but require Workgroup Security.

My Questions are: Is this really what I need to do to accomplish my goal?
Is there an easier way? For the programs that don’t need synchronization;
would I still have to convert to SQL Server to maintain the Security? I’m
willing to learn whatever I need to but my client would like this done as
soon as possible and I’m overwhelmed by the changes that need to be done.
Does anyone have suggestions as to where to start and how to proceed?

 

[AccessVandal via AccessMonster.com]

I can't say much about SharePoint as I don't use them.

What security you're talking about? MDB format file security? The ACCDB
format does not support that security anymore.

If you're moving to SQL Server, use the server security options instead. What
the point of using the outdated MDB security?

There no conversion needed, a little tweak in your code is all you need but
nothing like rewriting all objects or recreating objects. ( or I'm missing
something that you might have to do that?)

If you already know about spliting your database in Access, it should not be
a problem of connection to a SQL Server.

 

[Unknown Name]

WHAT DO U MEAN?????

 

[Albert D. Kallal]

My article here outlines some solutions and approaches for you:

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

 

[o;;]

I have designed many databases using various versions of Microsoft Access.
I
now have a need to upgrade to Access 2007. I have just read 1400 page
book
on 2007 and have searched microsoft's web and I still am confused about
the
best way to proceed.

I have a client that has a Head Office in one city and a Branch Office in
another city. They want to be able to synchronize databases. I am
considering converting to Access 2007 and using Sharepoint. This client
uses
2 of my Access 2000 programs. These 2 programs are very large. They both
link to 122 Tables and have a combined total of approximately 600 Queries,
380 Forms, 280 Reports and over 3,000 Subroutines. Also, Workgroup
Security
is essential.

To keep the Security, I need to use SQL Server or Sharepoint. To move the
Database to Sharepoint I have to convert to an accdb. These changes will
require a lot of updates to my programs and changes to the subroutines.
One
example is: Sharepoint lists don't support Referential Integrity and
Cascade
deletes which I rely on heavily in the programs. There are many other
examples.

This seems to be a huge undertaking.

I also have another large program in Access 2003 and many smaller ones.
Sometime in the future I'm sure I will have to upgrade to 2007. They don't
require synchronization but require Workgroup Security.

My Questions are: Is this really what I need to do to accomplish my goal?
Is there an easier way? For the programs that don't need synchronization;
would I still have to convert to SQL Server to maintain the Security? I'm
willing to learn whatever I need to but my client would like this done as
soon as possible and I'm overwhelmed by the changes that need to be done.
Does anyone have suggestions as to where to start and how to proceed?

 

[o;;]

I have designed many databases using various versions of Microsoft Access.
I
now have a need to upgrade to Access 2007. I have just read 1400 page
book
on 2007 and have searched microsoft's web and I still am confused about
the
best way to proceed.

I have a client that has a Head Office in one city and a Branch Office in
another city. They want to be able to synchronize databases. I am
considering converting to Access 2007 and using Sharepoint. This client
uses
2 of my Access 2000 programs. These 2 programs are very large. They both
link to 122 Tables and have a combined total of approximately 600 Queries,
380 Forms, 280 Reports and over 3,000 Subroutines. Also, Workgroup
Security
is essential.

To keep the Security, I need to use SQL Server or Sharepoint. To move the
Database to Sharepoint I have to convert to an accdb. These changes will
require a lot of updates to my programs and changes to the subroutines.
One
example is: Sharepoint lists don't support Referential Integrity and
Cascade
deletes which I rely on heavily in the programs. There are many other
examples.

This seems to be a huge undertaking.

I also have another large program in Access 2003 and many smaller ones.
Sometime in the future I'm sure I will have to upgrade to 2007. They don't
require synchronization but require Workgroup Security.

My Questions are: Is this really what I need to do to accomplish my goal?
Is there an easier way? For the programs that don't need synchronization;
would I still have to convert to SQL Server to maintain the Security? I'm
willing to learn whatever I need to but my client would like this done as
soon as possible and I'm overwhelmed by the changes that need to be done.
Does anyone have suggestions as to where to start and how to proceed?

 

[o;;]

I can't say much about SharePoint as I don't use them.

What security you're talking about? MDB format file security? The ACCDB
format does not support that security anymore.

If you're moving to SQL Server, use the server security options instead.
What
the point of using the outdated MDB security?

There no conversion needed, a little tweak in your code is all you need
but
nothing like rewriting all objects or recreating objects. ( or I'm missing
something that you might have to do that?)

If you already know about spliting your database in Access, it should not
be
a problem of connection to a SQL Server.

 

[o;;]

WHAT DO U MEAN?????

 

[o;;]

My article here outlines some solutions and approaches for you:

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

 

[o;;]

 

[o;;]

 

[ggregg]

Thank you for the information.