access and sql

hey,
i want to use access as a back-end database and sql as front-end .
i already made the entire access db but not the db in sql !
how do i start ?
THANKS IN ADVANCE
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
You can't make SQL Server the front-end, at least not with commonly
accepted definitions of the terms front-end and back-end. If you are
trying to link to a Jet database from SQL Server, see SQL BooksOnline
in the "Adding a linked server" topic.
--Mary
On Tue, 21 Dec 2004 13:19:40 -0800, vincent arntjen
<arntjenvincent@.hotmail.com> wrote:

>hey,
>i want to use access as a back-end database and sql as front-end .
>i already made the entire access db but not the db in sql !
>how do i start ?
>THANKS IN ADVANCE
>
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!

Access add record button grayed

Hi:
I have an MS ACCESS App that acts as a Front-End and SQL Server 2000 as
Back-End. I have the problem that dependent tables in the E-R model can't add
records, the add new record button is grayed, however the independent table
and catalog table have no problems, all tables have PK defined. Any ideas?
Thanks in advance
Regards
Hugo
The really depends on how you have done the data sources for
your forms. It's not really a SQL Server issue but more of a
MS Access issue. You will probably want to post this in one
of the MS Access newsgroups instead.
-Sue
On Wed, 25 Jul 2007 14:46:00 -0700, ijazbof
<ijazbof@.discussions.microsoft.com> wrote:

>Hi:
> I have an MS ACCESS App that acts as a Front-End and SQL Server 2000 as
>Back-End. I have the problem that dependent tables in the E-R model can't add
>records, the add new record button is grayed, however the independent table
>and catalog table have no problems, all tables have PK defined. Any ideas?
>Thanks in advance
>Regards
>Hugo

Access add record button grayed

Hi:
I have an MS ACCESS App that acts as a Front-End and SQL Server 2000 as
Back-End. I have the problem that dependent tables in the E-R model can't ad
d
records, the add new record button is grayed, however the independent table
and catalog table have no problems, all tables have PK defined. Any ideas?
Thanks in advance
Regards
HugoThe really depends on how you have done the data sources for
your forms. It's not really a SQL Server issue but more of a
MS Access issue. You will probably want to post this in one
of the MS Access newsgroups instead.
-Sue
On Wed, 25 Jul 2007 14:46:00 -0700, ijazbof
<ijazbof@.discussions.microsoft.com> wrote:

>Hi:
> I have an MS ACCESS App that acts as a Front-End and SQL Server 2000 as
>Back-End. I have the problem that dependent tables in the E-R model can't a
dd
>records, the add new record button is grayed, however the independent table
>and catalog table have no problems, all tables have PK defined. Any ideas?
>Thanks in advance
>Regards
>Hugo

Access 2003 Front End for SQL 2005

Hello,
I have a Microsoft Access front-end for a SQL 2005 database. The Access
front-end was in SQL 2000 and worked perfectly. When I migrated it to 2005,
I relinked the database and I can view the information, but I am unable to
add anything to the database. All of the Add Record functions have been
disabled.
Does anyone know why this is happening?
- Stewart
Nevermind, I figured it out. When I did the replication, SQL 2005 did not
copy over the Primary Key and Foreign Key Relationships. I manually
recreated them and it all woks fine...
"Stewart" <stewart@.nospam.com> wrote in message
news:%23$zL6TK5FHA.3880@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a Microsoft Access front-end for a SQL 2005 database. The Access
> front-end was in SQL 2000 and worked perfectly. When I migrated it to
> 2005, I relinked the database and I can view the information, but I am
> unable to add anything to the database. All of the Add Record functions
> have been disabled.
> Does anyone know why this is happening?
> - Stewart
>

Access + ODBC + MS SQL on WAN

Hi, there !
Can anybody tell me why the application MS ACCESS 2002
front-end + MS SQL Server 2000 back-end with the tables
linked via ODBC is running perfectly well on LAN, and does
not run on WAN ?
The firewall and security issues excluded.
Many thanks,
Dmitri KalininWhat do you mean by 'Does not run'
Is it slow? Crashes?
"Dmitri" <kalinin@.dblink.co.nz> wrote in message
news:081301c33f95$46100d80$a101280a@.phx.gbl...
> Hi, there !
> Can anybody tell me why the application MS ACCESS 2002
> front-end + MS SQL Server 2000 back-end with the tables
> linked via ODBC is running perfectly well on LAN, and does
> not run on WAN ?
> The firewall and security issues excluded.
> Many thanks,
> Dmitri Kalinin|||"Dmitri" <kalinin@.dblink.co.nz> wrote in message news:<081301c33f95$46100d80$a101280a@.phx.gbl>...
> Hi, there !
> Can anybody tell me why the application MS ACCESS 2002
> front-end + MS SQL Server 2000 back-end with the tables
> linked via ODBC is running perfectly well on LAN, and does
> not run on WAN ?
> The firewall and security issues excluded.
> Many thanks,
> Dmitri Kalinin
I'd guess there are different network protocols involved somehow.
Or maybe DNS.
Perhaps you need a LMhosts file (update)?

Access / SQL Server 2000 Redistributable

Hello,
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end?
Thanks,
Christy Warner.
Christy Warner
www.autoaudit.com
1) Yes, they will have to purchase a copy of SQL Server standard edition.
2) Most people use a DSN, and then have an install script. This install
script can either create the database and schema, and populate it with data,
or they attach a database withe the schema and data in place.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:79169CF3-5804-47D1-B91B-59791AB1037C@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end?
> Thanks,
> Christy Warner.
> --
> Christy Warner
> www.autoaudit.com
>
|||What's wrong with MSDERelA? It's free!
Cons: No Enterprise Manager (but who needs it?)
HTH. Aubrey
"Hilary Cotter" wrote:

> 1) Yes, they will have to purchase a copy of SQL Server standard edition.
> 2) Most people use a DSN, and then have an install script. This install
> script can either create the database and schema, and populate it with data,
> or they attach a database withe the schema and data in place.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:79169CF3-5804-47D1-B91B-59791AB1037C@.microsoft.com...
>
>