Re: SQL Tables

Roy,

No, and ADPs/ADEs use OLE/DB, not ODBC.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------

"RoyS29" <RoyS29@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9F5EBCD2-96F0-4EED-9FF8-D5A8097421E7@xxxxxxxxxxxxxxxx
Graham and Rob, thanks again for your replies. One more question, will
each
user who gets a copy of the ADE file need to have an ODBC connection
established to the SQL server?

Thanks,

"Graham R Seach" wrote:

Roy,

<<...which become stored procedures.>>
No. Queries do not "become" stored procedures. The Queries remain
queries,
albeit transferred to SQL Server. In SQL Server, a query is called a
"view".
Stored procedures are collections of SQL statements, much like a VBA
procedure, except they're in SQL. If you want stored procedures, you'll
have
to create them yourself.

<<...I'm not really distributing tables and queries...>>
Correct.

<<...how can I make sure it automatically connects...>>
Robert has already answered that.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------

"RoyS29" <RoyS29@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:169A926E-1309-432B-87BF-8059D9A0335C@xxxxxxxxxxxxxxxx
Graham, Thank you for your response. So, let see if I understand. If
I
import the tables back into my front end database, then upsize to the
MDB
file, the tables and queries (which become stored procedures) actually
reside
on the server. Ok, so if I distribute a copy of the MDB, I'm not
really
distributing tables and queries because they reside on the sql server,
correct? Also, if I distribute the MDB how can I make sure it
automatically
connects to the SQL database?

Thanks again for your help.

Roy

"Graham R Seach" wrote:

You're familiar with the concept of splitting the database. Well, an
ADP
is
the same kind of architecture, except the backend is SQL Server,
instead
of
Access. In an ADP, the tables (and data), and views (queries) are in
SQL
Server. You will also have access to stored procedures (which are not
present in Access), and database diagrams (although Access offers a
single
relationships diagram, SQL Server allows you to create many more of
them).

To get your data into SQL Server, it's probably easiest to import your
backend tables to your frontend, then use the Upsizing Wizard (Tools |
Database Utilities | Upsizing Wizard) to get them into SQL Server.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------

"RoyS29" <RoyS29@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:32D4C8B8-DBB2-4881-BFFA-5514F961635C@xxxxxxxxxxxxxxxx
I'm trying to convert a complex .MDB database into .ADP. This is
all
new
to
me so I'm learning. I have read here that ADp files don't have
data.
If
this is so, where is the data? Currently all my data resides on an
MDB
file
(I long ago split the code from the data). What do I have to do to
get
those
tables onto the SQL server so my MDP front end can see/connect to
them?
Please be very clear with your answer as this is all very new to me.

Thanks,








.

Relevant Pages

  • Re: Actually...
    ... "Graham R Seach" wrote: ... MsgBox "Duplicate Entry" ... Microsoft Access MVP ...
    (microsoft.public.access.formscoding)
  • RE: Actually...
    ... "Graham R Seach" wrote: ... Microsoft Access MVP ... MsgBox "Duplicate Entry" ...
    (microsoft.public.access.formscoding)
  • Re: Filter a drop down list?
    ... There are too many same counties with different states and it gets ... "Graham R Seach" wrote: ... >> Microsoft Access MVP ...
    (microsoft.public.access.forms)
  • Re: Two forms, one entry
    ... Microsoft Access MVP ... Graham R Seach wrote: ... shuts down the application, the login form unloads, firing the Unload ...
    (microsoft.public.access.formscoding)
  • Re: New Post - Owner deleted - No backups, nothing!
    ... Graham: Thanks for your help on this! ... "Graham R Seach" wrote: ... order to discover the Admin password. ... Microsoft Access MVP ...
    (microsoft.public.access.security)
Loading