Access Front End - SQL Backend?

[Aaron Shover]

Is there any way to create an access front-end of an SQL
database? Thus the SQL Database would serve as the
backend. I tried going under Linked Tables (in access
FILE-GET EXTERNAL DATA) but when I linked tables it
brought them in ok, but it will not allow me to add or
delete or even edit any records through Access. Did I do
something wrong, or is there another way to do it?
Thanks,
Aaron Shover

 

[Tim Ferguson]

Is there any way to create an access front-end of an SQL
database?

That's exactly what an ADP is...


Tim F

 

[Aaron Shover]

Excuse my ignorance, but I am not familiar with ADP. I've
heard of it but never knew what it meant...I'm still a
college student, so what I'm doing is for my internship,
so I still have lots to learn. If you could direct me to
some websites or places where I could learn about ADP I
would appreciate it. HOWEVER. I did get it to run as I
wanted.
Thanks for your help,
Aaron Shover

 

[Kevin @ 3NF]

Sounds like a permission error if you were not able to alter the records,
but were able to link to the tables. I am assuming you created a DSN to the
SQL Server...

 

[Kevin @ 3NF]

microsoft.public.access.adp.sqlserver is a ADP specific group

 

[Tim Ferguson]

Excuse my ignorance, but I am not familiar with ADP. I've
heard of it but never knew what it meant...I'm still a
college student, so what I'm doing is for my internship,
so I still have lots to learn. If you could direct me to
some websites or places where I could learn about ADP I
would appreciate it.

The best source of help is simply the Access help files, and projects
should loom large in any Access book.

To make an ADP, just go to File..New.. and choose Project(New Database).
From there you will be taken through the steps of locating your SQL server
and creating the database.

If you already have a SQL server database to base things on, choose
Project(Existing Database) instead.

From there on in, it's pretty much the same as any Access database: design
the tables and the relationships, create the queries (although in SQL S
these are views, which are practically the same thing) and then make your
forms and your reports. Some of the dialogs are different -- for example,
the table design window -- but the underlying stuff is not far different.
Once you get used to the ways in which SQL Server works differently from
Jet, you'll feel right at home.

Hope that helps.

Tim F