I need some confirmation. Is there any document from Microsoft that states n
o
changes need to be made to 32Bit Windows based Client/Server apps to access
data on a 64Bit SQL Server?
We code with VB6 an use MDAC to access our SQL Server DB, if a client wants
to move his SQL Server to a 64Bit machine and purchase a 64Bit SQL version,
we need to confirm that our will still work on his platform.
I am sure it will seeing as the DB engine is a seperate entity from our
application, but I just need an official document or link to a MS webpage
that states this.
Thanks.Hi
http://www.microsoft.com/sql/64bit/...o/overview.mspx
and especially
http://www.microsoft.com/sql/64bit/.../datasheet.mspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Poncho@.home" wrote:
> I need some confirmation. Is there any document from Microsoft that states
no
> changes need to be made to 32Bit Windows based Client/Server apps to acces
s
> data on a 64Bit SQL Server?
> We code with VB6 an use MDAC to access our SQL Server DB, if a client want
s
> to move his SQL Server to a 64Bit machine and purchase a 64Bit SQL version
,
> we need to confirm that our will still work on his platform.
> I am sure it will seeing as the DB engine is a seperate entity from our
> application, but I just need an official document or link to a MS webpage
> that states this.
> Thanks.|||Thanks, that is exactly what I needed.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> http://www.microsoft.com/sql/64bit/...o/overview.mspx
> and especially
> http://www.microsoft.com/sql/64bit/.../datasheet.mspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Poncho@.home" wrote:
>
Showing posts with label based. Show all posts
Showing posts with label based. Show all posts
Thursday, March 22, 2012
Thursday, March 8, 2012
20536: Unable to logon server
I have VB 6.0 Application calling Crystal Report 7.0 based on SQL Server 2000 datbase.
I use the LogonServer method with parameter p2ssql.dll to make the database connection.
I have used the above method for my Crystal Report for last 6 years and worked fine until now but now I get the "20536: Unable to logon server " in few XP OS machines.
This again works in the test XP machine I have used, I have almost tried all things I can try to fix the problem.
Does anyone have similar problems and if so how they dealt with it.
Any help in this regard is highly appreciated.
ThanksHigher security levels in XP, at a guess.
Do you have subreports??
If so, you may find that before your OS was allowing subreports to use login info from parent report, but now is breaking because OS demands you supply login info for each subreport.
In which case. iterate thru subreports collection and supply same login info to each subreport.
dave
I use the LogonServer method with parameter p2ssql.dll to make the database connection.
I have used the above method for my Crystal Report for last 6 years and worked fine until now but now I get the "20536: Unable to logon server " in few XP OS machines.
This again works in the test XP machine I have used, I have almost tried all things I can try to fix the problem.
Does anyone have similar problems and if so how they dealt with it.
Any help in this regard is highly appreciated.
ThanksHigher security levels in XP, at a guess.
Do you have subreports??
If so, you may find that before your OS was allowing subreports to use login info from parent report, but now is breaking because OS demands you supply login info for each subreport.
In which case. iterate thru subreports collection and supply same login info to each subreport.
dave
Thursday, February 16, 2012
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIA
when you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIA
when you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Licensing file based db's
I noticed it seems like 2k5 supports file based dbs... and I had a few
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weems
hi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weems
hi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
2005 Licensing file based db's
I noticed it seems like 2k5 supports file based dbs... and I had a few
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weemshi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weemshi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
2005 Licensing file based db's
I noticed it seems like 2k5 supports file based dbs... and I had a few
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weemshi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
quick questions...
1) does it require me to have sql2k server installed on machines I
deploy my apps to, to use the file based dbs?
2) what kind of licensing surrounds the file based dbs?
Thanks in advance
Weston Weemshi Weston,
Weston Weems wrote:
> I noticed it seems like 2k5 supports file based dbs... and I had a few
> quick questions...
> 1) does it require me to have sql2k server installed on machines I
> deploy my apps to, to use the file based dbs?
> 2) what kind of licensing surrounds the file based dbs?
> Thanks in advance
> Weston Weems
if you mean "User Instances" (AKA RANU) please have a look at
http://tinyurl.com/9obd8
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Saturday, February 11, 2012
2005 Datepicker control and dateformat
Hi, we have an installation of MSSQL reporting services where users
can select data based on date ranges. Since upgrading to 2005 we now
have a nice new Date picker control alongside textareas which accept
MSSQL datetime values.
This is all very nice but the date picker automatically formats the
date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
I
have checked the regional settings of both the browser/ server etc.
Scouring the Internet seems to point that this is a post SP2 problem
but there seems to be no fix other than making the datefields a type
of nvarchar and then converting them to dates in the Stored
Procedure.
If there really is no fix, how can I just disable this date picker
control? In 2000 people just entered the dates manually, this was
fine
but know there is a date picker control people are obviously going to
use it.
Thanks
RexOn Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> Hi, we have an installation of MSSQL reporting services where users
> can select data based on date ranges. Since upgrading to 2005 we now
> have a nice new Date picker control alongside textareas which accept
> MSSQL datetime values.
> This is all very nice but the date picker automatically formats the
> date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> I
> have checked the regional settings of both the browser/ server etc.
> Scouring the Internet seems to point that this is a post SP2 problem
> but there seems to be no fix other than making the datefields a type
> of nvarchar and then converting them to dates in the Stored
> Procedure.
> If there really is no fix, how can I just disable this date picker
> control? In 2000 people just entered the dates manually, this was
> fine
> but know there is a date picker control people are obviously going to
> use it.
> Thanks
> Rex
Aside from the workarounds you have attempted, that is also all I can
think of. If I understand you correctly, to remove the date time
picker in a specific report you would just select the Layout view ->
Report drop-down tab -> Report Parameters... and select the parameter
you want to remove the date time picker for and then change the Data
type: to something other than DateTime. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
> On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
>
>
> > Hi, we have an installation of MSSQL reporting services where users
> > can select data based on date ranges. Since upgrading to 2005 we now
> > have a nice new Date picker control alongside textareas which accept
> > MSSQL datetime values.
> > This is all very nice but the date picker automatically formats the
> > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > I
> > have checked the regional settings of both the browser/ server etc.
> > Scouring the Internet seems to point that this is a post SP2 problem
> > but there seems to be no fix other than making the datefields a type
> > of nvarchar and then converting them to dates in the Stored
> > Procedure.
> > If there really is no fix, how can I just disable this date picker
> > control? In 2000 people just entered the dates manually, this was
> > fine
> > but know there is a date picker control people are obviously going to
> > use it.
> > Thanks
> > Rex
> Aside from the workarounds you have attempted, that is also all I can
> think of. If I understand you correctly, to remove the date time
> picker in a specific report you would just select the Layout view ->
> Report drop-down tab -> Report Parameters... and select the parameter
> you want to remove the date time picker for and then change the Data
> type: to something other than DateTime. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant- Hide quoted text -
> - Show quoted text -
Hi Enrique, thanks for your help. I have found a fix which seems to
work so I'm posting here to help anyone in the future who comes across
the problem.
In the folder where Reporting Services is installed fin a file called
ReportView.aspx
e.g.
c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
\ReportServer\Pages\ReportViewer.aspx
Open up this file and add the following to the Page Directive
Culture="en-AU"
This seemed to solve my problem
Regards
Rex|||On Jul 5, 10:17 pm, Markus...@.gmail.com wrote:
> On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
>
> > On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> > > Hi, we have an installation of MSSQL reporting services where users
> > > can select data based on date ranges. Since upgrading to 2005 we now
> > > have a nice new Date picker control alongside textareas which accept
> > > MSSQL datetime values.
> > > This is all very nice but the date picker automatically formats the
> > > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > > I
> > > have checked the regional settings of both the browser/ server etc.
> > > Scouring the Internet seems to point that this is a post SP2 problem
> > > but there seems to be no fix other than making the datefields a type
> > > of nvarchar and then converting them to dates in the Stored
> > > Procedure.
> > > If there really is no fix, how can I just disable this date picker
> > > control? In 2000 people just entered the dates manually, this was
> > > fine
> > > but know there is a date picker control people are obviously going to
> > > use it.
> > > Thanks
> > > Rex
> > Aside from the workarounds you have attempted, that is also all I can
> > think of. If I understand you correctly, to remove the date time
> > picker in a specific report you would just select the Layout view ->
> > Report drop-down tab -> Report Parameters... and select the parameter
> > you want to remove the date time picker for and then change the Data
> > type: to something other than DateTime. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant- Hide quoted text -
> > - Show quoted text -
> Hi Enrique, thanks for your help. I have found a fix which seems to
> work so I'm posting here to help anyone in the future who comes across
> the problem.
> In the folder where Reporting Services is installed fin a file called
> ReportView.aspx
> e.g.
> c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> \ReportServer\Pages\ReportViewer.aspx
> Open up this file and add the following to the Page Directive
> Culture="en-AU"
> This seemed to solve my problem
> Regards
> Rex
Very nice tidbit to know. So basically, that manually changed your
regional settings I guess.
Regards,
Enrique Martinez
Sr. Software Consultant
can select data based on date ranges. Since upgrading to 2005 we now
have a nice new Date picker control alongside textareas which accept
MSSQL datetime values.
This is all very nice but the date picker automatically formats the
date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
I
have checked the regional settings of both the browser/ server etc.
Scouring the Internet seems to point that this is a post SP2 problem
but there seems to be no fix other than making the datefields a type
of nvarchar and then converting them to dates in the Stored
Procedure.
If there really is no fix, how can I just disable this date picker
control? In 2000 people just entered the dates manually, this was
fine
but know there is a date picker control people are obviously going to
use it.
Thanks
RexOn Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> Hi, we have an installation of MSSQL reporting services where users
> can select data based on date ranges. Since upgrading to 2005 we now
> have a nice new Date picker control alongside textareas which accept
> MSSQL datetime values.
> This is all very nice but the date picker automatically formats the
> date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> I
> have checked the regional settings of both the browser/ server etc.
> Scouring the Internet seems to point that this is a post SP2 problem
> but there seems to be no fix other than making the datefields a type
> of nvarchar and then converting them to dates in the Stored
> Procedure.
> If there really is no fix, how can I just disable this date picker
> control? In 2000 people just entered the dates manually, this was
> fine
> but know there is a date picker control people are obviously going to
> use it.
> Thanks
> Rex
Aside from the workarounds you have attempted, that is also all I can
think of. If I understand you correctly, to remove the date time
picker in a specific report you would just select the Layout view ->
Report drop-down tab -> Report Parameters... and select the parameter
you want to remove the date time picker for and then change the Data
type: to something other than DateTime. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
> On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
>
>
> > Hi, we have an installation of MSSQL reporting services where users
> > can select data based on date ranges. Since upgrading to 2005 we now
> > have a nice new Date picker control alongside textareas which accept
> > MSSQL datetime values.
> > This is all very nice but the date picker automatically formats the
> > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > I
> > have checked the regional settings of both the browser/ server etc.
> > Scouring the Internet seems to point that this is a post SP2 problem
> > but there seems to be no fix other than making the datefields a type
> > of nvarchar and then converting them to dates in the Stored
> > Procedure.
> > If there really is no fix, how can I just disable this date picker
> > control? In 2000 people just entered the dates manually, this was
> > fine
> > but know there is a date picker control people are obviously going to
> > use it.
> > Thanks
> > Rex
> Aside from the workarounds you have attempted, that is also all I can
> think of. If I understand you correctly, to remove the date time
> picker in a specific report you would just select the Layout view ->
> Report drop-down tab -> Report Parameters... and select the parameter
> you want to remove the date time picker for and then change the Data
> type: to something other than DateTime. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant- Hide quoted text -
> - Show quoted text -
Hi Enrique, thanks for your help. I have found a fix which seems to
work so I'm posting here to help anyone in the future who comes across
the problem.
In the folder where Reporting Services is installed fin a file called
ReportView.aspx
e.g.
c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
\ReportServer\Pages\ReportViewer.aspx
Open up this file and add the following to the Page Directive
Culture="en-AU"
This seemed to solve my problem
Regards
Rex|||On Jul 5, 10:17 pm, Markus...@.gmail.com wrote:
> On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
>
> > On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> > > Hi, we have an installation of MSSQL reporting services where users
> > > can select data based on date ranges. Since upgrading to 2005 we now
> > > have a nice new Date picker control alongside textareas which accept
> > > MSSQL datetime values.
> > > This is all very nice but the date picker automatically formats the
> > > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > > I
> > > have checked the regional settings of both the browser/ server etc.
> > > Scouring the Internet seems to point that this is a post SP2 problem
> > > but there seems to be no fix other than making the datefields a type
> > > of nvarchar and then converting them to dates in the Stored
> > > Procedure.
> > > If there really is no fix, how can I just disable this date picker
> > > control? In 2000 people just entered the dates manually, this was
> > > fine
> > > but know there is a date picker control people are obviously going to
> > > use it.
> > > Thanks
> > > Rex
> > Aside from the workarounds you have attempted, that is also all I can
> > think of. If I understand you correctly, to remove the date time
> > picker in a specific report you would just select the Layout view ->
> > Report drop-down tab -> Report Parameters... and select the parameter
> > you want to remove the date time picker for and then change the Data
> > type: to something other than DateTime. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant- Hide quoted text -
> > - Show quoted text -
> Hi Enrique, thanks for your help. I have found a fix which seems to
> work so I'm posting here to help anyone in the future who comes across
> the problem.
> In the folder where Reporting Services is installed fin a file called
> ReportView.aspx
> e.g.
> c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> \ReportServer\Pages\ReportViewer.aspx
> Open up this file and add the following to the Page Directive
> Culture="en-AU"
> This seemed to solve my problem
> Regards
> Rex
Very nice tidbit to know. So basically, that manually changed your
regional settings I guess.
Regards,
Enrique Martinez
Sr. Software Consultant
Subscribe to:
Posts (Atom)