Re: Upsizing .mdb for split DB

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Daran Johnson (daranj_at_hotmail.com)
Date: 03/25/04


Date: Thu, 25 Mar 2004 12:15:36 -0800

Joel,

The upsize procedure would only apply to the Access database that contains
the data (tables). The forms, reports, VBA etc. would remain in Access as
an ADP. Also, code that references data will have to be re-written. I
would also suggest that you take advantage of Stored Procedures. Books On
Line (BOL) is the best resource. You can find it at Microsoft's website.
There are a number of good books on the topic. I would suggest that you
begin to see this as an Access (ADP) front-end and a SQL Server back-end. I
think that will make the transition easier because some of the issues that I
have read in this newsgroup have more to do with continuing to see the new
system the same way as the old - as one product (i.e. MSDE is a part of
Access like JET is a part of Access).

Remember that you are moving to a true client/server system. The queries
and tables will now be on the server and that is where the work will be done
and the results will be sent to the client where that forms, reports,
macros, and VBA will be. I like to think of the ADP development environment
as a window to the tables, views, stored procedures, and functions residing
on the server. The forms, reports, macros, and VBA are local and in the
file you are working on. When you cannot connect to the server you will
still see the forms, reports, macros, and VBA but not the tables, views,
stored procedures, and functions.

I hope that helps.

-Daran

"Joel Wiseheart" <anonymous@discussions.microsoft.com> wrote in message
news:1365501c4128e$fe1e4870$a401280a@phx.gbl...
> Hello,
> I have found reference materials that discuss how to
> use the "Upsizing Wizard" to upsize from an .mdb file to
> a SQL/MSDE file. Th eproblem is that all the reference
> materials that I have found assume that you're upsizing a
> single, self-contained .mdb file.
> Is there any guides to upsize a from a Jet DB to a
> SQL/MSDE DB & .adp file, that has already been split, so
> the tables are in one .mdb file and the queries (and
> forms, reports, VBA etc.) are in another?
>
> Thanks!



Relevant Pages

  • Next step: Visual Studio?
    ... the user workstations and BE tables on a server. ... the SQL Server are good, so I just need to rewrite the adp Forms and Reports, ... I'm good with the Access design interface for Forms and Reports. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upsizing .mdb for split DB
    ... the queries from another .mdb file. ... The forms, reports, VBA etc. would ... Server back-end. ...
    (microsoft.public.access.adp.sqlserver)
  • RE: Queries VS VBA Design
    ... I manage a one million record database set up just that way. ... They log into the server and use the data they need through ... that are used to power different forms and reports that various users use. ... who will do not write VBA but do work extensively with queries. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: ADP Applications
    ... Likey these applications were not designed well. ... code for each part of reports formatting event is rather impressive. ... are doing mailing labels, or invoicing, or financial reports, the ms-access ... and generally perform just as well as ADP ...
    (comp.databases.ms-access)
  • Re: Future of ADPs
    ... SQL Server 2005 Express and ASP.Net, ... so I learned SQL-Server and ADP projects. ... that Microsoft really doesn't have an ... Reports to design your reports. ...
    (microsoft.public.access.adp.sqlserver)