Frustrating Authentication Errors

I have a prospective client evaluating our software that uses a SQL backend
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions'make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions'

Front-end input error checking or backend...?

This maybe belongs in the Data-Access Forum, but I'm not sure.

Is it generally a better idea to enforce things like unique constraints in the Database or the Webform? Say for example I want to make sure no duplicate Social Security Numbers are entered. Is it better to have an "If Exists" clause in my query, with a function to deal with it in the application or is it better to just fire the data to SQL Server and let the unique constraint on the dbase column deal with it? I then still have to have some code in my application to deal with the potential exisatance of that number, so is it a case of tomatoe, tomahtoe? If I understand things correctly, SQL server will return an error code if the piece of data does exist, and I will be able to parse the error code and display a message to the user.

Are there performance/coding issues involved? Best practices?In ASP.NET use Validator controls and to disallow duplicates make your table UNIQUE INDEX compatible because SQL Server will not allow the creation of UNIQUE INDEX on Columns that already include duplicate values. Include IGNORE_DUP_KEY in your create INDEX statement. Which means you are using both the application and the database. Hope this helps.

Kind regards,
Gift Peddie

front/backend access application--conversion to MSSQL--advice

I have an application that uses Acces as a backend and VBA as front end. Application is secured and is supplied on a CD with setup.exe.

Can I use VB 2005 and MS SQL to achieve the same?

Would I be able to package my application with all the neccessery files (assuming that client does not have any e.g. SQL server) so that multiple front ends can access data from common source?

Would I be able to secure such an application using only VS 2005?

What would I need to quickly learn how to achieve the above ( any books you can suggest maybe)?

You can absolutely use SQL Server Express to ship as part of your application - it is designed for that. You can find a whitepaper with guidance on this at http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/emsqlexcustapp.asp. The whitepaper includes an explanation of how you can use a feature called ClickOnce in Visual Studio/.NET to deploy your client applications. You should also sign up for redistribution rights for Express at http://www.microsoft.com/sql/editions/express/redistregister.mspx.

Thanks< MJ

from access to sql

hope you can help.

I need to get my access db backend to sql. I have tried the upsizing
wizard but the get message "overflow" and cannot get any further.

I also use queries that reference two date ranges from forms such as
BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
this in an sql view?You will need lots of advice. I suggest that you buy "Microsoft Access
Developer's Guide to SQL Server". It's awesome and will answer all your
questions, and save you countless hours of frustration.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz

"Mark" <maworrell@.ananzi.co.za> wrote in message
news:ddbf09eb.0310231219.20065b09@.posting.google.c om...
> hope you can help.
> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.
> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?|||One option for you. Just a thought. We use Borland Delphi as the main
language at work. It comes with an upsizing tool called 'Data Pump'
which is really useful for taking data from one db to another. I use
this quite a bit for Access -> SQL transfers. It may be worthwhile
doing a few searches on the Internet for this to see if Borland or
anyone else can help with a similar tool. We get it bundled with
Delphi (I think it's available with Paradox as well), but it may be
available as a seperate tool.

The problem you will have is with getting the structure copied over to
SQL. If you can find a way of creating the correct table structure in
the SQL db, then you can easily link the table through ODBC into
Access and import the data through a query. Problem is the structure
has to be there already.

If you only have a few tables and they aren't too big, I'd look at
creating them by hand on SQL instead of spending time looking for ways
to move the data. Moving the data is the easy bit.

"Jerry Boone" <jerry@.antech.biz.nospam> wrote in message news:<Z7rub.1119$LL3.330@.newssvr23.news.prodigy.com>...
> You will need lots of advice. I suggest that you buy "Microsoft Access
> Developer's Guide to SQL Server". It's awesome and will answer all your
> questions, and save you countless hours of frustration.
> --
> Jerry Boone
> Analytical Technologies, Inc.
> http://www.antech.biz
>
> "Mark" <maworrell@.ananzi.co.za> wrote in message
> news:ddbf09eb.0310231219.20065b09@.posting.google.c om...
> > hope you can help.
> > I need to get my access db backend to sql. I have tried the upsizing
> > wizard but the get message "overflow" and cannot get any further.
> > I also use queries that reference two date ranges from forms such as
> > BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> > this in an sql view?|||Mark:

> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.

Check this kb:

http://support.microsoft.com/suppor...s/q272/3/84.asp

> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?

Might want to look into stored procedures or user defined functions.
You could also apply your criteria after the view is defined. IE:
Select MyInfo from MyView Where MyDateCol Between '2002-12-12' and
'2002-10-12'.

HTH.

BZ

maworrell@.ananzi.co.za (Mark) wrote in message news:<ddbf09eb.0310231219.20065b09@.posting.google.com>...
> hope you can help.
> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.
> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?