I need to be able to look up the install path for sql from within a DTS
package. The registry reading stored procs have been deleted for 'security'
but I need to make sure that SQL Agent has full access to the directory for a
temp file. It would be ideal to get the install path and use that. This DTS
will be installed an mulitple instances so I would like to automate this.Thom,
Maybe REGEDT32 and look for SQLPath?
HTH
Jerry
"Thom" <Thom@.discussions.microsoft.com> wrote in message
news:7A48EA99-65D1-4ECF-B996-84191EF2DA64@.microsoft.com...
>I need to be able to look up the install path for sql from within a DTS
> package. The registry reading stored procs have been deleted for
> 'security'
> but I need to make sure that SQL Agent has full access to the directory
> for a
> temp file. It would be ideal to get the install path and use that. This
> DTS
> will be installed an mulitple instances so I would like to automate this.
Showing posts with label package. Show all posts
Showing posts with label package. Show all posts
Wednesday, March 28, 2012
Install Package: VB6.0 w/ SQL Server 2000
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
Christy Warner
www.autoaudit.com
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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?
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.
|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
>
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>
|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
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
Christy Warner
www.autoaudit.com
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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?
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.
|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
>
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>
|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
Install Package: VB6.0 w/ SQL Server 2000
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
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server.
I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc
.
>
> People mass-market SQL Server specific products all the time. You basical
ly
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home use
rs
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, an
d
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>
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
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server.
I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc
.
>
> People mass-market SQL Server specific products all the time. You basical
ly
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home use
rs
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, an
d
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>
Install Package: VB6.0 w/ SQL Server 2000
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
--
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
> Access suffers from the same 2 GB limitation on database size.
> > 1) will my customers have to purchase SQL Server 2000?
> > (or me, and then give them the copy w/ my app).
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
> > 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'
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
>> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
>> Access suffers from the same 2 GB limitation on database size.
>> > 1) will my customers have to purchase SQL Server 2000?
>> > (or me, and then give them the copy w/ my app).
>> If MSDE is not an option, your customers should probably have SQL Server.
>> I
>> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
>> your app, as you don't necessarily know your clients' licensing needs,
>> etc.
>> > 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'
>> People mass-market SQL Server specific products all the time. You
>> basically
>> need to test it on SQL Server and make sure you specify it in the system
>> requirements for your app. A quick question - are you selling to home
>> users
>> or businesses? If you're selling to individual home users or small
>> businesses, you might reconsider using MSDE, as it is freely available,
>> and
>> the 2 GB restriction shouldn't be so bad for an app that previously ran
>> on
>> Access.
>>
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
--
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 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'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
> Access suffers from the same 2 GB limitation on database size.
> > 1) will my customers have to purchase SQL Server 2000?
> > (or me, and then give them the copy w/ my app).
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
> > 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'
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
>> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.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:
>> Access suffers from the same 2 GB limitation on database size.
>> > 1) will my customers have to purchase SQL Server 2000?
>> > (or me, and then give them the copy w/ my app).
>> If MSDE is not an option, your customers should probably have SQL Server.
>> I
>> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
>> your app, as you don't necessarily know your clients' licensing needs,
>> etc.
>> > 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'
>> People mass-market SQL Server specific products all the time. You
>> basically
>> need to test it on SQL Server and make sure you specify it in the system
>> requirements for your app. A quick question - are you selling to home
>> users
>> or businesses? If you're selling to individual home users or small
>> businesses, you might reconsider using MSDE, as it is freely available,
>> and
>> the 2 GB restriction shouldn't be so bad for an app that previously ran
>> on
>> Access.
>>
Wednesday, March 21, 2012
install dtsrun utility
Hello everybody,
I need to install the dtsrun util on a client who needs to call a dts package. I want to do this without enterprise manager.
We had no problem in the past withWin NT 4 client. Right now, I try to
install this dtsrun utility on a Win2k pro client and when I do regsvr32
dtsffile.dll
The instructions are explained on redist.txt on the sql server CD rom.
I receive each time the message that I can't register the dll.
Can anyone point me in some direction ?
Thanks,
Bjorn
this is the information I found :
INSTALLATION NOTES FOR DATA TRANSFORMATION SERVICES (DTS)
------------------
The following files must be registered using the regsvr32.exe utility:
dtsffile.dll
dtspkg.dll
dtspump.dll
axscphst.dll
Example: regsvr32 80\Tools\Binn\dtsffile.dll
The sqlunirl.dll file should reside in the system folder (i.e.,
\winnt\system32 or \windows\system).in the Text Box type: regsvr32 d:\YourDir\YourFile
where "d:\YourDir\YourFile" is the full path to the dll's.
Seems like you may have left out the c:\pf\MSQLS\80\...\file.dll
Hope this may help...
To unregister it, type in the text box: regsvr32 /u d:\YourDir\YourFile
NOTE: The full path of the dll must be enclosed as regsvr32 "c:\PF\MSLS\80\your.dll" to succeed.|||Also this file may be used to register dll's by right clicking with the shift key
I need to install the dtsrun util on a client who needs to call a dts package. I want to do this without enterprise manager.
We had no problem in the past withWin NT 4 client. Right now, I try to
install this dtsrun utility on a Win2k pro client and when I do regsvr32
dtsffile.dll
The instructions are explained on redist.txt on the sql server CD rom.
I receive each time the message that I can't register the dll.
Can anyone point me in some direction ?
Thanks,
Bjorn
this is the information I found :
INSTALLATION NOTES FOR DATA TRANSFORMATION SERVICES (DTS)
------------------
The following files must be registered using the regsvr32.exe utility:
dtsffile.dll
dtspkg.dll
dtspump.dll
axscphst.dll
Example: regsvr32 80\Tools\Binn\dtsffile.dll
The sqlunirl.dll file should reside in the system folder (i.e.,
\winnt\system32 or \windows\system).in the Text Box type: regsvr32 d:\YourDir\YourFile
where "d:\YourDir\YourFile" is the full path to the dll's.
Seems like you may have left out the c:\pf\MSQLS\80\...\file.dll
Hope this may help...
To unregister it, type in the text box: regsvr32 /u d:\YourDir\YourFile
NOTE: The full path of the dll must be enclosed as regsvr32 "c:\PF\MSLS\80\your.dll" to succeed.|||Also this file may be used to register dll's by right clicking with the shift key
install DTS package
Hi guys!
How do you install a DTS package from another server.
I have a .dts file (coming from another SQL Server) and I want to transfer it to another SQL Server?
Please advise.
Thanks!
Assuming this is SQL 2000, in enterprise manager right click on the DTS node and select open package(in 7.0 this is all tasks open package). The package should now be open in the designer, now just save it locally as normal.|||http://www.sqldts.com/204.aspxMonday, March 19, 2012
Installation - How do you get it to run?
I have downloaded the SQLce package from Microsoft and have run the .msi file.
How do I actually start the product and create tables and data?
Thanks,
Fred
You can't. It only really runs as part of your code (or someone else's).
If you want to create tables, etc. you're probably going to want to use SQL Server Management Studio, the express version is free.
Friday, March 9, 2012
Inserts failed sometimes ...
We have installed a package developed by another company and sometimes
(when the server is with a big rate of transactions), we are seeing
the following messages in package debug file:
(when the server is with a big rate of transactions), we are seeing
the following messages in package debug file:
2004-04-22 14:23:27 3056:
------------------
2004-04-22 14:23:27 3056: rlm03000: ls_PutOneRecord: Failed inserting
[04113SO07236054]
2004-04-22 14:23:27 3056: ODBCSetCursorName[3056]: Failed specifying
cursor concurrency to statement handle 1 for 'ls_rep_add'
2004-04-22 14:23:27 3056: dbc01003: ODBCSetCursorName[3056]:
ls_rep_add generated SQL error state: 24000
2004-04-22 14:23:27 3056: dbc01002: [Microsoft][ODBC Driver Manager]
Invalid cursor state
2004-04-22 14:23:27 3056: odbcFilterConnectErrors[3056]: set the
iState to ODBC_DISCONNECT for <24000>
2004-04-22 14:23:27 3056: Function Return Code [00001] ODBC_ERROR
2004-04-22 14:23:27 3056: Operation [00000] ls_PutOneRecord
2004-04-22 14:23:27 3056: Primary Return Code [00000] 00000
2004-04-22 14:23:27 3056: Secondary Return Code [0000000001] 00000
2004-04-22 14:23:27 3056:
------------------
When this message appears in the app debug file we are loosing some
inserts that the application do in the database.
The MS SQL server configuration is:
4 Pentium 760Mhz 4 GB RAM
SQL 2000 Standard Edition 8.00.760 SP 4
MDAC 2.7 driver ODBC SQLSRV32.dll 2000.81.9031.14 15/11/2002
Any tip will be welcome,
Thanks in advance,
ReisRobson Reis (reisrf@.yahoo.com) writes:
> We have installed a package developed by another company and sometimes
> (when the server is with a big rate of transactions), we are seeing
> the following messages in package debug file:
I'm afraid that this is not an issue that is easy resolved over a
newsgroup. The best would of course be to open a support case with
that vendor. If you don't have a support contract or that vendor
has gone bust, you may have to find some who can reverse-engineer
the package, or who can dig up the source code.
Judging from the log and your mentioning of heavy stress, I would
guess that there is poor error handling in conjunction with deadlocks.
A poor workaround could be to run this package against an idle
environment, and then replicate from that environment in your live
environment.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Robson Reis" <reisrf@.yahoo.com> wrote in message
news:33bf8ee4.0405061045.7cab35af@.posting.google.c om...
> We have installed a package developed by another company and sometimes
> (when the server is with a big rate of transactions), we are seeing
> the following messages in package debug file:
>
> 2004-04-22 14:23:27 3056:
> ------------------
> 2004-04-22 14:23:27 3056: rlm03000: ls_PutOneRecord: Failed inserting
> [04113SO07236054]
> 2004-04-22 14:23:27 3056: ODBCSetCursorName[3056]: Failed specifying
> cursor concurrency to statement handle 1 for 'ls_rep_add'
> 2004-04-22 14:23:27 3056: dbc01003: ODBCSetCursorName[3056]:
> ls_rep_add generated SQL error state: 24000
> 2004-04-22 14:23:27 3056: dbc01002: [Microsoft][ODBC Driver Manager]
> Invalid cursor state
> 2004-04-22 14:23:27 3056: odbcFilterConnectErrors[3056]: set the
> iState to ODBC_DISCONNECT for <24000>
> 2004-04-22 14:23:27 3056: Function Return Code [00001] ODBC_ERROR
> 2004-04-22 14:23:27 3056: Operation [00000] ls_PutOneRecord
> 2004-04-22 14:23:27 3056: Primary Return Code [00000] 00000
> 2004-04-22 14:23:27 3056: Secondary Return Code [0000000001] 00000
> 2004-04-22 14:23:27 3056:
> ------------------
> When this message appears in the app debug file we are loosing some
> inserts that the application do in the database.
> The MS SQL server configuration is:
> 4 Pentium 760Mhz 4 GB RAM
> SQL 2000 Standard Edition 8.00.760 SP 4
> MDAC 2.7 driver ODBC SQLSRV32.dll 2000.81.9031.14 15/11/2002
>
> Any tip will be welcome,
> Thanks in advance,
> Reis
As I understand it, the error messages you've listed come from your
application log, not from SQL Server, so the first place to go for support
should be the application vendor.
You might get more information in microsoft.public.sqlserver.odbc or
..jdbcdriver, but without more knowledge of what the application is, what the
code looks like, and what the app is doing when this error occurs, it's
almost impossible to give more help.
Simon
Wednesday, March 7, 2012
Insertion / updation problem in SSIS
“I have a scenario where i am trying to insert 200,000 lac records & update 200,000 lac record in destination table using SISS Package (SQL SERVER 2005) but I am not able to neither update nor insert the records . while executing the package its not showing any error also . what could be the problem ? “ We have completed upto move to flat destination files using raw files, could you please help to move this flat files data (for update) to database. what logic we need to use? is it required to add dataflow diagram after raw file destination component
|||
We have business logic in Package creation 1) Insert New records and 2) Update Existing Records using the follow Data flow diagram
For update we are using OLEDB command, for insert we are using OLEDB Destination.
We are using merge join for spliting record into insert and update.
Perhaps there is blocking on the destination table. This can often happen if you're attempting 2 operations simultaneously.
Execute sp_who2 to see if there's any blocking going on.
-Jamie
|||is there any other solution for this problem, is this not possible to run for achive both insertion and updation in the same package? if i try to run the package for less records, it is succeded, if i try to run the package for more records, then same problem coming again and again
Thanks & Regards
S.Nagarajan
|||In that case I am even more sure that blocking is a problem. Did you bother to execute sp_who2 like I advised?
There is an easy fix to this problem. Continue to do the insert but push teh adta to be updated into a raw file. You can then use the contents of the raw file in another data-flow in order to do the update,.
-Jamie
|||I ran sp_who2 and found the blocking, how can i remove the blocking, is there any query to remove the blocking. I couldn't get your solution clearly, please brief me your alternate solution.|||Do you know what raw files are? If not, go away and study them. When you have finished read #1 here: http://blogs.conchango.com/jamiethomson/archive/2006/02/17/2877.aspx
It describes a different scenario for using raw files but the usage is the same.
-Jamie
|||
Please stop writing the same question in multiple threads simultaneously. People are here to help and don't want to waste their time clicking through and reading the same thing more than once.
-Jamie
Sunday, February 19, 2012
Inserting Nulls with DTS
I am using a DTS package to copy data from a flat file to a table. I need for fields that are empty to be changed to nulls in the output. I wrote a VB Script to do this, but now it takes about 10 times longer that when I used the Copy transformation. Is there a faster way to do this?
I haven't tried the Trim transformation yet. (I'm waiting for my load to finish.) Will that place nulls in the output if a field is empty?Originally posted by jsneeringer
I am using a DTS package to copy data from a flat file to a table. I need for fields that are empty to be changed to nulls in the output. I wrote a VB Script to do this, but now it takes about 10 times longer that when I used the Copy transformation. Is there a faster way to do this?
I haven't tried the Trim transformation yet. (I'm waiting for my load to finish.) Will that place nulls in the output if a field is empty?
Hi,
1-in your SQL Server Table ( Destination DB) set a default value for the field(s), so when you attemp to insert Null value in that Field, the specified default vale will be insert. ( the way of inserting is not important . It can be DTS!!)
2- you can also write a Instead Of Trigger on your Table For Insert, so process the field value, if it's Null , write empty.
Hope that help you
I haven't tried the Trim transformation yet. (I'm waiting for my load to finish.) Will that place nulls in the output if a field is empty?Originally posted by jsneeringer
I am using a DTS package to copy data from a flat file to a table. I need for fields that are empty to be changed to nulls in the output. I wrote a VB Script to do this, but now it takes about 10 times longer that when I used the Copy transformation. Is there a faster way to do this?
I haven't tried the Trim transformation yet. (I'm waiting for my load to finish.) Will that place nulls in the output if a field is empty?
Hi,
1-in your SQL Server Table ( Destination DB) set a default value for the field(s), so when you attemp to insert Null value in that Field, the specified default vale will be insert. ( the way of inserting is not important . It can be DTS!!)
2- you can also write a Instead Of Trigger on your Table For Insert, so process the field value, if it's Null , write empty.
Hope that help you
Subscribe to:
Posts (Atom)