pdf instead of html as default output format

Hi all,
I would like to output all reports in pdf format instead of html.
I dont want to allow users to choose an export format.
So, if they access an URL and fill some textboxes with appropriated
parameters I can send them a ready-to-print PDF file in Internet Explorer.
Is it possible?
(I´m assuming all clients uses IE browser and Acrobat Reader plugin).
thanks a lot!One way you can do it is in the url of the report. You can add at the end of
your report url:
&rs:Command=Render&rs:format=pdf
Since it is in the url you have to be careful how you open it. I just open
the report in a new windows and it will actually render the report in the
adobe acrobat reader progam so there is no url the user can change. You
could embed it in an iframe on a page to display to a user as well.
"Ricardo" wrote:
> Hi all,
> I would like to output all reports in pdf format instead of html.
> I dont want to allow users to choose an export format.
> So, if they access an URL and fill some textboxes with appropriated
> parameters I can send them a ready-to-print PDF file in Internet Explorer.
> Is it possible?
> (I´m assuming all clients uses IE browser and Acrobat Reader plugin).
> thanks a lot!
>
>

Pbm Migrating Access 2003 Database to Sql 2005Express Edition

I tried various ways to migrate an access 2003 database with 1 table to

sql Express 2005 Edition without success, I can only find the resulted

sql database in Sql Server Express Edition 2005 without data.

Please advise if any help.

This article might help:

http://support.microsoft.com/kb/237980

Buck Woody

|||Check that you don't have any replication field in the table. This will cause it to fail in migration.sql

Pbm Migrating Access 2003 Database to Sql 2005Express Edition

I tried various ways to migrate an access 2003 database with 1 table to

sql Express 2005 Edition without success, I can only find the resulted

sql database in Sql Server Express Edition 2005 without data.

Please advise if any help.

This article might help:

http://support.microsoft.com/kb/237980

Buck Woody

|||Check that you don't have any replication field in the table. This will cause it to fail in migration.

PB using UNION ALL with VB6 and SQL-server

I'm working on a softwear and I have to create some Update. This softwear used first MS Access as a database, and now I have to create the code which allows it to use MS SQL-server. This softwear is created in VB6.

I've got some error when I'm using the UNION ALL function. This error appears:
"incorrect syntax towards the key word ' union' "

Here is the code in VB6 :

" GOpenLocalDb (FOR_READ) ' open the database

SQLStmt = "select * from ol_table_temp"
SQLStmt = SQLStmt & " where [Subject_no] = " & dlr_subject & " "
ord$ = SQL_Order()
SQLStmt = SQLStmt & ord$

'dalafouzos: 24/09/2002 I added the lines below to include the DLR entries in the ol_old table
SQLStmt = SQLStmt & " union all select * from ol_table_old where [Subject_no] = " & dlr_subject & " "
ord$ = SQL_Order()
SQLStmt = SQLStmt & ord$

'GOpenLocalDb (FOR_READ) ' open the database
Set DLRset = New ADODB.Recordset
DLRset.CursorLocation = adUseClient
DLRset.Open SQLStmt, g_objConn, adOpenKeyset, adLockReadOnly, adCmdText "

when the error appears the value of SQLStmt is :

"select * from ol_table_temp where [Subject_no] = 1020 Order by [Date] DESC, [Time] DESC union all select * from ol_table_old where [Subject_no] = 1020 Order by [Date] DESC, [Time] DESC "

Thanks for your help...and both tables has the same DDL?|||I think so. Both of them are similar...but how can I see if they have the same DDL? because I'm not sure as I didn't have to create these tables.

But this syntaxe works well with MS Access...the problem appears only with MS SQL-server.sql

PB to connect a remote.

hi,

last week I posted a thread to explain that I was unable tu access a remote sqlserver from my personnal computer running wsindows XP.
I had a problem with my motherboard which obliged me to change it. I did, and decided to format my hard drive and reinstal only the programs needed, once upon SQL server could connect to my DB. I first instal XP, then the SP1 and after sql server. Then i configured the client network utility using an alias and giving the IP. It functionned well. Then I instal the soft I need (Sharp developp, webmatrix, flash XP (ftp), Together and office XP) but I was configuring Outlook when I got and CPU FAN warning. 256 mega de ram later, I was sure it will run like it did saturday but it was'nt. It make the same error as before the motherboard changing. So I reformat my hard drive and I don't understand what could it make weel run on satruday and the shunt down on monday.

so If you have an Idea of what to do, please help me,

wozoiI reinstall XP but not the SP1 and just SQL server it make the same eternal error connection open conect()).

somebody get an idea.

wozoi|||Please post the exact error and also any entries in the event log and your sql server log.|||hi and thanks,

On the remote server ther is no trace of a connection trying,
and i don't find on my computer the event log you asks.

In the Attachement you will find the screen shot and the translation (because I'm french) of the error.

Could you reply me where can i find the event log to send it to you.

thanks for your help.

pierre jean

Password Required on Open of Linked Access mdb file

Any help would be great. I have an mdb file that is linked
to a table on my SQL Server which resides on a corporate
Web Server. I have a non-Windows Authenticated username
and password to the SQL Server database, so I have to
enter the password everytime I open the Access database
that links to the SQL Server. Is there anywhere to store
my password so that I can bypass having to enter it
everytime I open a linked mdb? Thanks!That information is stored in the tabledef properties of the linked
tables. One solution to this problem is to write code when the
application starts up. The code creates new tabledef objects,
supplying the user name and password (which you can collect from a
form). When the application shuts down, delete the tabledef objects.
This way security information persists only for the life of the
application instead of being permanently cached with the linked
tables.
--mary
On Mon, 3 May 2004 16:01:07 -0700, "mj"
<anonymous@.discussions.microsoft.com> wrote:

>Any help would be great. I have an mdb file that is linked
>to a table on my SQL Server which resides on a corporate
>Web Server. I have a non-Windows Authenticated username
>and password to the SQL Server database, so I have to
>enter the password everytime I open the Access database
>that links to the SQL Server. Is there anywhere to store
>my password so that I can bypass having to enter it
>everytime I open a linked mdb? Thanks!

Password Required on Open of Linked Access mdb file

Any help would be great. I have an mdb file that is linked
to a table on my SQL Server which resides on a corporate
Web Server. I have a non-Windows Authenticated username
and password to the SQL Server database, so I have to
enter the password everytime I open the Access database
that links to the SQL Server. Is there anywhere to store
my password so that I can bypass having to enter it
everytime I open a linked mdb? Thanks!
That information is stored in the tabledef properties of the linked
tables. One solution to this problem is to write code when the
application starts up. The code creates new tabledef objects,
supplying the user name and password (which you can collect from a
form). When the application shuts down, delete the tabledef objects.
This way security information persists only for the life of the
application instead of being permanently cached with the linked
tables.
--mary
On Mon, 3 May 2004 16:01:07 -0700, "mj"
<anonymous@.discussions.microsoft.com> wrote:

>Any help would be great. I have an mdb file that is linked
>to a table on my SQL Server which resides on a corporate
>Web Server. I have a non-Windows Authenticated username
>and password to the SQL Server database, so I have to
>enter the password everytime I open the Access database
>that links to the SQL Server. Is there anywhere to store
>my password so that I can bypass having to enter it
>everytime I open a linked mdb? Thanks!

Password protected Access 2000 DB

Hi everyone,

I'm having a problem connecting to my Access 2000 DB from VB.net 2003. The DB has an password protection, but no username/password protection. So, no .mdw files are used, only the DB own Jet password. At desing-mode, when connecting to DB first time, I'm asked the username (blanc) password (blanc) and the Jet database password ('myPass'). Everything works just fine until when I try to debug the program. Database login dialogbox appears and asks for username and password, but no Jet database password... So, I'm unable to connect. PLEASE help me on this one, because I starting to lose my mind while trying to find the answer. Thx in advance.

Jari@.FinlandPlease help. I'm desperate.|||I'm STILL strugging with this problem. Somebody, please help me. I've tried every solution presented on this forum (and every other that I was able to find) but the problem still exists. I managed to change the db path, userID and password at runtime, but can't find a way to enter the DB password... If I remove the password from DB everything works just fine. Even with normal logon information (userID & password). The TableLogOnInfo class doesn't give the option for DB password, only the UserID and password. The ConnectionInfo class has a password-option but I'm not sure is this for the DB password or what? And how should I use this class? I'll paste some code for you to see.

Dim oCRTab As New CrystalDecisions.Shared.TableLogOnInfo
Dim oCRConn As New CrystalDecisions.Shared.ConnectionInfo

Dim tab As Table
Dim report As New MyReport
tab = report .Database.Tables("MyTable")
oCRConn.Password = "TheDBPass"

oCRTab.ConnectionInfo = oCRConn
oCRTab.ConnectionInfo.ServerName = "c:\dbTest\db1.mdb"
oCRTab.TableName = "MyTable"

tab.ApplyLogOnInfo(oCRTab)

And later I bind the report to the CRViewer and it still asks for the login information...|||Yep, talking to myself again. Found out the solution to the problem: there isn't any... I received a post from businessobjects and found out this:

====================
NOTE:

You cannot set a database level password when
using Crystal Reports for Visual Studio .NET 2002 or
2003.
====================

So back to square one. I quess I'll have to find some other way to do my reports.

antijape .......boycottin CR since 2005.......

Password Proctected Excel Subscription

I need to send protected information via a reporting services subscripiton. Unfortunately the receiver can not access our reporting services web page so I have to send it as an excel attachment with email. Is there a way I can protect the spreadsheet automatically before it is sent via the subscription.

Thanks

Reporting Services doesn't currently have a DRM/IRM or Excel password feature, so you would have to post-process the Excel files that RS generates.|||Thanks but I'm still not sure how I'd do that without programming.|||You will have to do some programming, or open the Excel files in Excel and modify them.

Password Parameter?

Hello.
I've got an odd requirement to password a particular report.Basically
the same authenticated user will have access to all reports, but this
particular report should only be available to select users(all which
share that username).
Any way to mask an ssrs parameter input so that it only shows *******?
Any way to persist that entry for 5 minutes, then have it no long be
valid. I've not tested or developed this yet, but I do suspect if I
call the report again (from asp.net reportviewer) and the default for
the parameter is null, that the previously entered value will not be
available right?
I currently have another post where i can't seem to figure out why my
report is defaulting some fields that no longer have fields, but only
when I test the report through reportviewer, and not my vs.net on my
client.
Thanks for any help or information!it would probably be better to put the report into a separate folder and
secure it via the folder. this would allow to have multiple reports with
this security requirement in the future. Parameters are not really intended
for passwords.
"jobs" <jobs@.webdos.com> wrote in message
news:1193496978.830252.227650@.v23g2000prn.googlegroups.com...
> Hello.
> I've got an odd requirement to password a particular report.Basically
> the same authenticated user will have access to all reports, but this
> particular report should only be available to select users(all which
> share that username).
> Any way to mask an ssrs parameter input so that it only shows *******?
> Any way to persist that entry for 5 minutes, then have it no long be
> valid. I've not tested or developed this yet, but I do suspect if I
> call the report again (from asp.net reportviewer) and the default for
> the parameter is null, that the previously entered value will not be
> available right?
> I currently have another post where i can't seem to figure out why my
> report is defaulting some fields that no longer have fields, but only
> when I test the report through reportviewer, and not my vs.net on my
> client.
> Thanks for any help or information!
>

Password Input Mask

In access there is an input mask for a field of type "password". Is there anything similar in SQL Server 2000?No, but you can remove the select permission in the password column in your database|||Access_dude: paradigm shift required...

While Access is a combination database engine and application interface, SQL Server does not have a built-in application interface. Masks, and many other interface features of MS Access are not in SQL Server.

blindman

password encryption

I have an Access .adp application and I need to store the passwords encrypted. I see that there are unsupported functions pwdencrypt() and pwdcompare() in SQL server 2K.
Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?

SQL Server 2000 encryption is pretty weak. 2005 is supposed to address this. In the meantime, you might consider this link:

http://www.sqlservercentral.com/columnists/mcoles/freeencryption.asp

(you may have to register, but registration is free).

Alternatively, you could use the Micrsoft Crypto API (capicom.dll) or the .Net Encryption utilities (don't have more specific references on these).

Regards,

hmscott

Password column in a database table

I need to "mask" the password entries in a table. Access has a simple solution but I can not find a way to do this in SQL. This does not have to be encrypted, just hid
from the few users we have internally with SQL logins to the database. Any helpful tips or help files would be much appreciated!
No masking available. Hashing, encryption are at your disposal, but better
is you have the option of column level permissions or just simply create a
view without that column and provide these users access to that view.
That's exactly how it is supposed to be done.
hth
Eric
CRouse wrote:
> I need to "mask" the password entries in a table. Access has a
> simple solution but I can not find a way to do this in SQL. This does
> not have to be encrypted, just hid from the few users we have
> internally with SQL logins to the database. Any helpful tips or help
> files would be much appreciated!
|||In SQL Server 2000, you can apply column-level permissions or deny those
users select access to the table.
There is no "mask" functionality unless you actually encrypt or encode the
data.
http://www.aspfaq.com/
(Reverse address to reply.)
"CRouse" <CRouse@.discussions.microsoft.com> wrote in message
news:690C479A-498A-470E-B8F2-A8912A5D42EC@.microsoft.com...
> I need to "mask" the password entries in a table. Access has a simple
solution but I can not find a way to do this in SQL. This does not have to
be encrypted, just hid
> from the few users we have internally with SQL logins to the database.
Any helpful tips or help files would be much appreciated!

Password column in a database table

I need to "mask" the password entries in a table. Access has a simple solut
ion but I can not find a way to do this in SQL. This does not have to be enc
rypted, just hid
from the few users we have internally with SQL logins to the database. Any
helpful tips or help files would be much appreciated!No masking available. Hashing, encryption are at your disposal, but better
is you have the option of column level permissions or just simply create a
view without that column and provide these users access to that view.
That's exactly how it is supposed to be done.
hth
Eric
CRouse wrote:
> I need to "mask" the password entries in a table. Access has a
> simple solution but I can not find a way to do this in SQL. This does
> not have to be encrypted, just hid from the few users we have
> internally with SQL logins to the database. Any helpful tips or help
> files would be much appreciated!|||In SQL Server 2000, you can apply column-level permissions or deny those
users select access to the table.
There is no "mask" functionality unless you actually encrypt or encode the
data.
http://www.aspfaq.com/
(Reverse address to reply.)
"CRouse" <CRouse@.discussions.microsoft.com> wrote in message
news:690C479A-498A-470E-B8F2-A8912A5D42EC@.microsoft.com...
> I need to "mask" the password entries in a table. Access has a simple
solution but I can not find a way to do this in SQL. This does not have to
be encrypted, just hid
> from the few users we have internally with SQL logins to the database.
Any helpful tips or help files would be much appreciated!

password case seasitive configuration

Hi, All,
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
MartinTo the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
change is documented in:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> Hi, All,
> I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> seasitive, anyone knows we can configure sql 2005 user password is not
> seasitive?
> Thanks for your time,
> Martin|||Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> > Hi, All,
> >
> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> > seasitive, anyone knows we can configure sql 2005 user password is not
> > seasitive?
> >
> > Thanks for your time,
> > Martin
>|||1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
collation for the system databases (AFAIK), which was decided when you installed the SQL Server
instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
and should be performed unless you have good knowledge of the SQL Server architecture and can
determine what such a rebuild will do.
2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
install 2005, and you find an like in the SQL Server program group.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> Hi, Tibor Karaszi,
> 1) if not in Sql 2005, do you know we can configute IIS web server is not
> case seasitive?
> 2) where to see
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> you tell how to go there.
> Thanks in advance,
> Martin
>
> "Tibor Karaszi" wrote:
>> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> behavior
>> change is documented in:
>> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> > Hi, All,
>> >
>> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> > seasitive, anyone knows we can configure sql 2005 user password is not
>> > seasitive?
>> >
>> > Thanks for your time,
>> > Martin
>>|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
> and should be performed unless you have good knowledge of the SQL Server architecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> > case seasitive?
> > 2) where to see
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> > you tell how to go there.
> >
> > Thanks in advance,
> > Martin
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> behavior
> >> change is documented in:
> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> > Hi, All,
> >> >
> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> > seasitive?
> >> >
> >> > Thanks for your time,
> >> > Martin
> >>
> >>
>|||That only applies to 2000, logins are *always* case sensitive in 2005.
If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
the consequences to running it, etc, before attempting this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> Hi, Tibor Karaszi,
> yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> for sql 2000 or sql 2005?
> Thanks
> "Tibor Karaszi" wrote:
>> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
>> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
>> instances. To change this, you need to use rebuildm.exe which will scratch all the system
>> databases,
>> and should be performed unless you have good knowledge of the SQL Server architecture and can
>> determine what such a rebuild will do.
>> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
>> install 2005, and you find an like in the SQL Server program group.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>> > Hi, Tibor Karaszi,
>> >
>> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
>> > case seasitive?
>> > 2) where to see
>> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
>> > can
>> > you tell how to go there.
>> >
>> > Thanks in advance,
>> > Martin
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> >> behavior
>> >> change is documented in:
>> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> >> > Hi, All,
>> >> >
>> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> >> > seasitive, anyone knows we can configure sql 2005 user password is not
>> >> > seasitive?
>> >> >
>> >> > Thanks for your time,
>> >> > Martin
>> >>
>> >>
>>|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> > for sql 2000 or sql 2005?
> >
> > Thanks
> >
> > "Tibor Karaszi" wrote:
> >
> >> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> >> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> >> instances. To change this, you need to use rebuildm.exe which will scratch all the system
> >> databases,
> >> and should be performed unless you have good knowledge of the SQL Server architecture and can
> >> determine what such a rebuild will do.
> >>
> >> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> >> install 2005, and you find an like in the SQL Server program group.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> >> > Hi, Tibor Karaszi,
> >> >
> >> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> >> > case seasitive?
> >> > 2) where to see
> >> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
> >> > can
> >> > you tell how to go there.
> >> >
> >> > Thanks in advance,
> >> > Martin
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> >> behavior
> >> >> change is documented in:
> >> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://www.solidqualitylearning.com/
> >> >>
> >> >>
> >> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> >> > Hi, All,
> >> >> >
> >> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> >> > seasitive?
> >> >> >
> >> >> > Thanks for your time,
> >> >> > Martin
> >> >>
> >> >>
> >>
> >>
>

Passing second column of table as index

We are working on C++ in eVC++ 3.0 environment (CE 3.0) with SQL CE 2.0.

We are trying with IRowsetIndex:: Seek method to access the data from the database.

We are facing problem when we try to access data from the table having composite index other than the first column.

For example:
The table ITEM contains the following columns:
1. ItemCode
2. PcNo
3. SubPcNo
4. BrandNo
5. DescText

6. ProductionKind

7. ProductionState

8. ClearingState

9. ST

10. TS

I’ve two indexes for this table where the two indexes are

1. ItemKey1 on ITEM (ItemCode).

2. ItemKey2 on ITEM (PcNo, SubPcNo, BrandNo).

If I mention ItemKey1 as the index then the Seek method works perfectly.

But if I mention ItemKey2 as the index, then I’m getting the error as “DB_E_BADBINDINFO”.

When we visted the MSDN for this problem we noted that:

1. When you use the Seek method on multiple fields, the Seek fields must be in the same order as the fields in the underlying table. If they are not, the Seek method fails.

2. When passing key values to an index rowset, the consumer performs these actions only for the number of key columns specified in the cKeyValues argument in IRowsetIndex:: Seek.

So we had the composite index such that columns of a composite index are physically aligned next to each other as in the table.

When the first column of the index is the first column of the table as in index ItemKey1 we found that the seek method works perfectly.

If we pass the index ItemKey2, we are again getting the error “DB_E_BADBINDINFO”.

What else have we missed out while passing the keys in IRowsetIndex:: Seek?

Thanks in advance.

Regards,

Sasi.

I saw this error when tried to use the table accessor for seeking. When you use IRowsetIndex you must create a separate accessor for the index columns and use that accessor for the Seek method, not the table's own accessor.

|||

Thanks for your reply Joao Paulo Figueira.

I was not able to understand the solution you provided, could you kinldy explain in detail.

Thanks & Regards,

Sasi.

|||

You must create a second memory buffer where to store the values to seek. This is built the same way as the memory buffer for accessing table data, but it must have the index columns and in the same order. You should use code similar to the one for binding the table columns in order to create the index accessor.

The only situation when you can share the same accessor between the table and the index is when the first N columns of the index are the same as the first N columns of the table. In all other situations you must create a different accessor for entering the data to seek.

|||

Thanks a lot Sir.

Its working now.

Thanks & Regards,

Sasi.