Pros vs Cons of installing MSDE on Win98 SE

Hi All,
Since I have not been able to get MSDE to work under Win2000 Pro while
logged in as a 'Power User' I have to come up with an alternative. I
have searched the MS knowledge base and posted a couple of questions
here but no one has been able to help me with this problem. I notice
that some other people have the same problem and they too were not able
to fix it.
So, my idea is to install MSDE on a Win98 SE computer. Anyone know if
this is a good/bad idea?
Thanks for any help,
Charles
"Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
news:eEzPbQ0EFHA.2824@.tk2msftngp13.phx.gbl...
> Hi All,
> Since I have not been able to get MSDE to work under Win2000 Pro while
> logged in as a 'Power User' I have to come up with an alternative. I have
> searched the MS knowledge base and posted a couple of questions here but
> no one has been able to help me with this problem. I notice that some
> other people have the same problem and they too were not able to fix it.
> So, my idea is to install MSDE on a Win98 SE computer. Anyone know if
> this is a good/bad idea?
MSDE on Win98SE works fine. With the notable exception of it not
automatically starting the services. Strangely this does not seem to happen
on all 98 installations. There is a workaround for (google that one).

>
> Thanks for any help,
> Charles
|||Plus, in our experience, it's much slower and way less reliable on FAT32
than on NTFS. FAT32 is great for sequential access, not good for random (as
in most databases). NTFS is a journalled filesystem. Words like
"cross-linked clusters" etc. are not words you want associated with your
database. If you are going to use it on Win98, I'd suggest leaving AutoClose
database option on for safety.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Tim Bird" <tim.bird@.nospamprettypleasehebron.co.uk> wrote in message
news:%23KgOn40EFHA.2700@.TK2MSFTNGP14.phx.gbl...
> "Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
> news:eEzPbQ0EFHA.2824@.tk2msftngp13.phx.gbl...
> MSDE on Win98SE works fine. With the notable exception of it not
> automatically starting the services. Strangely this does not seem to
> happen on all 98 installations. There is a workaround for (google that
> one).
>
>
|||Power User is not enough to install applications under. Get used to it as W2K
onwards, you have to live with it. Security. Security.Security.
Win 98 Or 98SE is no longer fully supported:
http://support.microsoft.com/gp/lifewin
Regards
Mike
"Greg Low [MVP]" wrote:

> Plus, in our experience, it's much slower and way less reliable on FAT32
> than on NTFS. FAT32 is great for sequential access, not good for random (as
> in most databases). NTFS is a journalled filesystem. Words like
> "cross-linked clusters" etc. are not words you want associated with your
> database. If you are going to use it on Win98, I'd suggest leaving AutoClose
> database option on for safety.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Tim Bird" <tim.bird@.nospamprettypleasehebron.co.uk> wrote in message
> news:%23KgOn40EFHA.2700@.TK2MSFTNGP14.phx.gbl...
>
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:64304A06-E8CD-4CEF-9BAA-93D53520CDB6@.microsoft.com...
> Power User is not enough to install applications under. Get used to it as
> W2K
> onwards, you have to live with it. Security. Security.Security.
> Win 98 Or 98SE is no longer fully supported:
> http://support.microsoft.com/gp/lifewin
I have to agree with both of you. MSDE will run on Win98 - but not as well.
Even though the sooner the message gets through to users about 98SE the
better, in the "real" world us developers still have to support Win98 and
sometimes even Win95 (Though thankfully not very often)!!!. And we still
occasionally get sales enquiries for Win3.11 installations!!!!!
[vbcol=seagreen]
> Regards
> Mike
> "Greg Low [MVP]" wrote:
|||Hi Mike,
I install MSDE while logged in as 'Administrator' and it installs fine.
It works fine as long as the person logged in has Administrator
rights. The problem is that I do not want to allow anyone to have
Administrator rights. Even I do not use a login with Administrator
rights. I, like all my users, only have 'Power User' rights and that's
the way I want to keep it.
When a 'Power User' logs in the service does not appear to start. The
SQL icon in the taskbar is blank (white circle). When I open it up
there is no computer name or services shown in the drop down lists. If
I type in the computer name and hit the 'Refresh' button then MSDE
starts to run but when I load a certain program (my ISP dialer software)
the MSI installer kicks in. Sometimes it appears to be installing but
then it rolls back and the little icon in the taskbar is gone. Other
times it just sits there and does nothing. Whatever happens the MSI
installer kicks in every time I load my ISP dialer software.
So, I install MSDE while logged in as 'Administrator' but I want MSDE to
run while anyone is logged in as a 'Power User' (without the MSI
installer kicking in every single time).
Thanks for any help,
Charles
On 2/15/2005 5:29 AM, Mike Epprecht (SQL MVP) wrote:[vbcol=seagreen]
> Power User is not enough to install applications under. Get used to it as W2K
> onwards, you have to live with it. Security. Security.Security.
> Win 98 Or 98SE is no longer fully supported:
> http://support.microsoft.com/gp/lifewin
> Regards
> Mike
> "Greg Low [MVP]" wrote:
>
|||I believe MSDE is still running on your system when logged in as a Power
User. The issue is that you do not have permissions to enumerate the names
of services. If you bring up Task Manager do you see sqlservr.exe running?
If you do then MSDE is up and ready for connections.
Jim
"Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
news:uKM%23xO2EFHA.2176@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Hi Mike,
> I install MSDE while logged in as 'Administrator' and it installs fine. It
> works fine as long as the person logged in has Administrator rights. The
> problem is that I do not want to allow anyone to have Administrator
> rights. Even I do not use a login with Administrator rights. I, like all
> my users, only have 'Power User' rights and that's the way I want to keep
> it.
> When a 'Power User' logs in the service does not appear to start. The SQL
> icon in the taskbar is blank (white circle). When I open it up there is
> no computer name or services shown in the drop down lists. If I type in
> the computer name and hit the 'Refresh' button then MSDE starts to run but
> when I load a certain program (my ISP dialer software) the MSI installer
> kicks in. Sometimes it appears to be installing but then it rolls back
> and the little icon in the taskbar is gone. Other times it just sits
> there and does nothing. Whatever happens the MSI installer kicks in every
> time I load my ISP dialer software.
> So, I install MSDE while logged in as 'Administrator' but I want MSDE to
> run while anyone is logged in as a 'Power User' (without the MSI installer
> kicking in every single time).
>
> Thanks for any help,
> Charles
> On 2/15/2005 5:29 AM, Mike Epprecht (SQL MVP) wrote:
|||Hi,
At the moment I have MSDE un-installed. I will re-install it later
today and report back.
Let's assume that what you say is true then my next questions are:
1. Why does the SQL icon even load up in the first place? If a 'Power
User' does not have the correct rights then the icon is useless.
2. Why does the MSDE installer kick in every single time my ISP dialer
is loaded? Any ideas on how to stop this?
Thanks for any help,
Charles
On 2/15/2005 9:50 AM, Jim Young wrote:[vbcol=seagreen]
> I believe MSDE is still running on your system when logged in as a Power
> User. The issue is that you do not have permissions to enumerate the names
> of services. If you bring up Task Manager do you see sqlservr.exe running?
> If you do then MSDE is up and ready for connections.
> Jim
> "Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
> news:uKM%23xO2EFHA.2176@.TK2MSFTNGP15.phx.gbl...
|||1.SQL Service Manager is placed in the Startup folder for All Users, so it
will run no matter who logs in. If you want you can remove it after MSDE is
installed.
2. Haven't a clue.
Jim
"Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
news:%23whnwW4EFHA.2608@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi,
> At the moment I have MSDE un-installed. I will re-install it later today
> and report back.
> Let's assume that what you say is true then my next questions are:
> 1. Why does the SQL icon even load up in the first place? If a 'Power
> User' does not have the correct rights then the icon is useless.
> 2. Why does the MSDE installer kick in every single time my ISP dialer is
> loaded? Any ideas on how to stop this?
>
> Thanks for any help,
> Charles
> On 2/15/2005 9:50 AM, Jim Young wrote:
|||Hi,
Ok, I have re-installed MSDE SP3 on my Win2000 Pro computer, then I
applied the KB815495 patch (this is the same process I have done
before). This time the SQL icon does work when logged in as a 'Power
User' but only until I load my ISP dialer software, then MSI installer
kicks in and fails, then the SQL icon disappears from the taskbar.
This time I checked the task manager and I did see 'sqlservr.exe'
process. I 'assume' this means that the SQL server is running. I did
not have time to actually test but will try in a couple of days.
The only problem that remains is the MSDE installer that kicks in every
time the ISP dialer software is loaded. This happens to all 'Power
Users' not just me. If I change the users group from 'Power User' to
'Administrators' then the problem disappears. But, I do not want to do
this. When I change the users group back to 'Power Users' the problem
appears again.
Now, if I can figure out why this happens, so I can stop it, I will be a
happy camper.
Thanks for your help,
Charles
On 2/15/2005 1:10 PM, Jim Young wrote:[vbcol=seagreen]
> 1.SQL Service Manager is placed in the Startup folder for All Users, so it
> will run no matter who logs in. If you want you can remove it after MSDE is
> installed.
> 2. Haven't a clue.
> Jim
> "Charles E Finkenbiner" <CharlesEF_@._MailandNews.Com> wrote in message
> news:%23whnwW4EFHA.2608@.TK2MSFTNGP10.phx.gbl...

Prompt for login credentials using Windows-NT Authentication

Hello,
I am using a SQL Server (MSDE) db, currently configured to only accept
Windows-NT Authentication logins. This has worked well for a while -
much easier to administer. However I have a group of users that have
presented a special problem.
These users have valid logins under a valid Windows Domain ie
<Domain>\<user>. Unlike most users, however, they do not login to the
windows domain when they log into their machines (instead they login
to the local machine). In cases other than mine, when they access
applications/web services that require authentication to the said
windows domain, they are prompted for login credentials (ie
username=<domain>\<user> and password). They can then proceed to use
the application/web service.
With my SQL Server database, however, this does not happen. When they
attempt to login to my database, I am guessing that the server figures
out that they are not currently logged in to the windows domain, so
denies them access outright. They are given no opportunity to enter
their credentials. They are attempting to access the database using
data access pages / OWC10.
Is there any way that I can setup a connection string which allows me
to continue using Windows-NT Authentication, but will prompt users for
login credentials if they are not currently logged in to the required
Windows Domain?
Thanks heaps for your help.
Nick TompsonIt's been a while since I've worked with data access pages, but as I
recollect the connection is hard-wired into the page. What I think
you're going to have to do is to provide a login where they can join
the domain that is accredited with your SQL Server prior to loading
the page. I could be wrong about this -- you might want to post the
question in the microsoft.public.access.dataaccess.pages ng.
-- Mary
On 2 May 2004 23:48:13 -0700, ntompson@.utas.edu.au (Nick Tompson)
wrote:

>Hello,
>I am using a SQL Server (MSDE) db, currently configured to only accept
>Windows-NT Authentication logins. This has worked well for a while -
>much easier to administer. However I have a group of users that have
>presented a special problem.
>These users have valid logins under a valid Windows Domain ie
><Domain>\<user>. Unlike most users, however, they do not login to the
>windows domain when they log into their machines (instead they login
>to the local machine). In cases other than mine, when they access
>applications/web services that require authentication to the said
>windows domain, they are prompted for login credentials (ie
>username=<domain>\<user> and password). They can then proceed to use
>the application/web service.
>With my SQL Server database, however, this does not happen. When they
>attempt to login to my database, I am guessing that the server figures
>out that they are not currently logged in to the windows domain, so
>denies them access outright. They are given no opportunity to enter
>their credentials. They are attempting to access the database using
>data access pages / OWC10.
>Is there any way that I can setup a connection string which allows me
>to continue using Windows-NT Authentication, but will prompt users for
>login credentials if they are not currently logged in to the required
>Windows Domain?
>Thanks heaps for your help.
>Nick Tompson|||If the users log on to the local machine then that is the login tha SQL
Server expects. You can workaround this problem by creating a user account
on the SQL Server machine with the same name and password as the users who
are logging in and grant that login a login within SQL Server. This should
allow them to log in to SQL Server using the local machine account.
Outside of that I am not sure there is a way, unless you can get the IIS
anonymous login to be used by these users.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thankyou both for your comments. I think that your solutions may work,
however, I am keen to stick with Windows-NT Authentication if I can, as
I do not want to have to manage usernames and passwords.
Any other ideas?
Thanks
Nick Tompson
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||If you don't want to create mirrored local accounts, you might try having
the users map a drive to a share on the SQL Server using their domain
account. I believe SQL Server will use these security credentials for the
trusted connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Nick Tompson" <ntompson@.utas.edu.au> wrote in message
news:uOTSDsWMEHA.3012@.tk2msftngp13.phx.gbl...
> Thankyou both for your comments. I think that your solutions may work,
> however, I am keen to stick with Windows-NT Authentication if I can, as
> I do not want to have to manage usernames and passwords.
> Any other ideas?
> Thanks
> Nick Tompson
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

Prompt for login credentials using Windows-NT Authentication

Hello,
I am using a SQL Server (MSDE) db, currently configured to only accept
Windows-NT Authentication logins. This has worked well for a while -
much easier to administer. However I have a group of users that have
presented a special problem.
These users have valid logins under a valid Windows Domain ie
<Domain>\<user>. Unlike most users, however, they do not login to the
windows domain when they log into their machines (instead they login
to the local machine). In cases other than mine, when they access
applications/web services that require authentication to the said
windows domain, they are prompted for login credentials (ie
username=<domain>\<user> and password). They can then proceed to use
the application/web service.
With my SQL Server database, however, this does not happen. When they
attempt to login to my database, I am guessing that the server figures
out that they are not currently logged in to the windows domain, so
denies them access outright. They are given no opportunity to enter
their credentials. They are attempting to access the database using
data access pages / OWC10.
Is there any way that I can setup a connection string which allows me
to continue using Windows-NT Authentication, but will prompt users for
login credentials if they are not currently logged in to the required
Windows Domain?
Thanks heaps for your help.
Nick TompsonIt's been a while since I've worked with data access pages, but as I
recollect the connection is hard-wired into the page. What I think
you're going to have to do is to provide a login where they can join
the domain that is accredited with your SQL Server prior to loading
the page. I could be wrong about this -- you might want to post the
question in the microsoft.public.access.dataaccess.pages ng.
-- Mary
On 2 May 2004 23:48:13 -0700, ntompson@.utas.edu.au (Nick Tompson)
wrote:
>Hello,
>I am using a SQL Server (MSDE) db, currently configured to only accept
>Windows-NT Authentication logins. This has worked well for a while -
>much easier to administer. However I have a group of users that have
>presented a special problem.
>These users have valid logins under a valid Windows Domain ie
><Domain>\<user>. Unlike most users, however, they do not login to the
>windows domain when they log into their machines (instead they login
>to the local machine). In cases other than mine, when they access
>applications/web services that require authentication to the said
>windows domain, they are prompted for login credentials (ie
>username=<domain>\<user> and password). They can then proceed to use
>the application/web service.
>With my SQL Server database, however, this does not happen. When they
>attempt to login to my database, I am guessing that the server figures
>out that they are not currently logged in to the windows domain, so
>denies them access outright. They are given no opportunity to enter
>their credentials. They are attempting to access the database using
>data access pages / OWC10.
>Is there any way that I can setup a connection string which allows me
>to continue using Windows-NT Authentication, but will prompt users for
>login credentials if they are not currently logged in to the required
>Windows Domain?
>Thanks heaps for your help.
>Nick Tompson|||If the users log on to the local machine then that is the login tha SQL
Server expects. You can workaround this problem by creating a user account
on the SQL Server machine with the same name and password as the users who
are logging in and grant that login a login within SQL Server. This should
allow them to log in to SQL Server using the local machine account.
Outside of that I am not sure there is a way, unless you can get the IIS
anonymous login to be used by these users.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Prompt for login credentials using Windows-NT Authentication

Hello,
I am using a SQL Server (MSDE) db, currently configured to only accept
Windows-NT Authentication logins. This has worked well for a while -
much easier to administer. However I have a group of users that have
presented a special problem.
These users have valid logins under a valid Windows Domain ie
<Domain>\<user>. Unlike most users, however, they do not login to the
windows domain when they log into their machines (instead they login
to the local machine). In cases other than mine, when they access
applications/web services that require authentication to the said
windows domain, they are prompted for login credentials (ie
username=<domain>\<user> and password). They can then proceed to use
the application/web service.
With my SQL Server database, however, this does not happen. When they
attempt to login to my database, I am guessing that the server figures
out that they are not currently logged in to the windows domain, so
denies them access outright. They are given no opportunity to enter
their credentials. They are attempting to access the database using
data access pages / OWC10.
Is there any way that I can setup a connection string which allows me
to continue using Windows-NT Authentication, but will prompt users for
login credentials if they are not currently logged in to the required
Windows Domain?
Thanks heaps for your help.
Nick Tompson
It's been a while since I've worked with data access pages, but as I
recollect the connection is hard-wired into the page. What I think
you're going to have to do is to provide a login where they can join
the domain that is accredited with your SQL Server prior to loading
the page. I could be wrong about this -- you might want to post the
question in the microsoft.public.access.dataaccess.pages ng.
-- Mary
On 2 May 2004 23:48:13 -0700, ntompson@.utas.edu.au (Nick Tompson)
wrote:

>Hello,
>I am using a SQL Server (MSDE) db, currently configured to only accept
>Windows-NT Authentication logins. This has worked well for a while -
>much easier to administer. However I have a group of users that have
>presented a special problem.
>These users have valid logins under a valid Windows Domain ie
><Domain>\<user>. Unlike most users, however, they do not login to the
>windows domain when they log into their machines (instead they login
>to the local machine). In cases other than mine, when they access
>applications/web services that require authentication to the said
>windows domain, they are prompted for login credentials (ie
>username=<domain>\<user> and password). They can then proceed to use
>the application/web service.
>With my SQL Server database, however, this does not happen. When they
>attempt to login to my database, I am guessing that the server figures
>out that they are not currently logged in to the windows domain, so
>denies them access outright. They are given no opportunity to enter
>their credentials. They are attempting to access the database using
>data access pages / OWC10.
>Is there any way that I can setup a connection string which allows me
>to continue using Windows-NT Authentication, but will prompt users for
>login credentials if they are not currently logged in to the required
>Windows Domain?
>Thanks heaps for your help.
>Nick Tompson
|||If the users log on to the local machine then that is the login tha SQL
Server expects. You can workaround this problem by creating a user account
on the SQL Server machine with the same name and password as the users who
are logging in and grant that login a login within SQL Server. This should
allow them to log in to SQL Server using the local machine account.
Outside of that I am not sure there is a way, unless you can get the IIS
anonymous login to be used by these users.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thankyou both for your comments. I think that your solutions may work,
however, I am keen to stick with Windows-NT Authentication if I can, as
I do not want to have to manage usernames and passwords.
Any other ideas?
Thanks
Nick Tompson
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||If you don't want to create mirrored local accounts, you might try having
the users map a drive to a share on the SQL Server using their domain
account. I believe SQL Server will use these security credentials for the
trusted connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Nick Tompson" <ntompson@.utas.edu.au> wrote in message
news:uOTSDsWMEHA.3012@.tk2msftngp13.phx.gbl...
> Thankyou both for your comments. I think that your solutions may work,
> however, I am keen to stick with Windows-NT Authentication if I can, as
> I do not want to have to manage usernames and passwords.
> Any other ideas?
> Thanks
> Nick Tompson
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
sql

Programming continuous merge replication

Hello,
This projects needs to setup automatically a few MSDE subscribers to a main
Distributor/Publisher.
I am using the ActiveX SQL Merge object to set up the merge replication, but
there are 3 problems:
1) There is not a property to set Continuous mode
2) If I set the ExchangeType to upload, when I browse for the properties
using Enterprise Manager, the “ExchangeType 1” is not present in the Agent
step
3) (Project killer) Assume I manage to set Continuous… After running the
SqlMerge object, the status shows “initializing in progress” but it never
finishes and I have to start again the agent from Enterprise Manager… after
selecting Start (from Enterprise Manager) the synchronization runs as
expected… but I cannot start it by program.
Here are the properties and methods that I am calling after everything is
already registered and ready:
//set up the publisher
m_oSqlMerge.Publisher = m_sDistServerName;
m_oSqlMerge.PublisherSecurityMode =
SQLMERGXLib.SECURITY_TYPE.DB_AUTHENTICATION;
m_oSqlMerge.PublisherDatabase = m_sDbName;
m_oSqlMerge.PublisherPassword = m_sDistPassword;
m_oSqlMerge.PublisherLogin = "sa";
m_oSqlMerge.Publication = m_sDbName;
//set up the distributor
m_oSqlMerge.Distributor = m_sDistServerName;
m_oSqlMerge.DistributorSecurityMode =
SQLMERGXLib.SECURITY_TYPE.NT_AUTHENTICATION;
//set up the subscriber
m_oSqlMerge.Subscriber = oSub.ServerName;
m_oSqlMerge.SubscriberDatabase = oSub.DatabaseName;
m_oSqlMerge.SubscriberDatasourceType =
SQLMERGXLib.DATASOURCE_TYPE.SQL_SERVER;
m_oSqlMerge.SubscriberSecurityMode =
SQLMERGXLib.SECURITY_TYPE.DB_AUTHENTICATION;
m_oSqlMerge.SubscriberLogin = "sa";
m_oSqlMerge.SubscriberPassword = sPassword;
//set up the subscription
m_oSqlMerge.SubscriptionType = SQLMERGXLib.SUBSCRIPTION_TYPE.PULL;
m_oSqlMerge.SynchronizationType =
SQLMERGXLib.SYNCHRONIZATION_TYPE.AUTOMATIC;
m_oSqlMerge.ExchangeType = SQLMERGXLib.EXCHANGE_TYPE.UPLOAD;
ProgressValue = 0;
//Initialize
m_oSqlMerge.Initialize();
m_oSqlMerge.Run();
//m_oSqlMerge.Terminate(); //No need to terminate if continuous
When you create a subscription to a merge publication using Enterprise
Manager, a SQL Server Agent job is created that, when run, synchronizes the
subscription. This job is used whenever you synchronize the subscription from
Enterprise Manager. However, when you start the synchronization
programmatically this agent job is not used and the Merge Agent is started
with the properties you set for the object instance. This is why setting
m_oSqlMerge.ExchangeType = SQLMERGXLib.EXCHANGE_TYPE.UPLOAD doesn’t affect
what you see in Enterprise Manager (which is the agent job). There is no
continuous mode for the Merge Agent, however, you can easily use a timer
control or program a method that calls the Run method at regular intervals to
synchronize the subscription. You should do some inserts at the Subscriber
and run the Merge Agent using your code to see if they make it to the
Publisher. Handling the Status event is a good way to get all of the agent
status and messages. For a good example of how to implement the Status event,
see http://www.winnetmag.com/Article/Art...79/39079.html. (Note you
need to be on at least SP3.)
Best Wishes,
Glenn Gailey [MS]
SQL Server User Education
"This posting is provided "AS IS" with no warranties, and confers no rights"
"uk" wrote:

> Hello,
> This projects needs to setup automatically a few MSDE subscribers to a main
> Distributor/Publisher.
> I am using the ActiveX SQL Merge object to set up the merge replication, but
> there are 3 problems:
> 1) There is not a property to set Continuous mode
> 2) If I set the ExchangeType to upload, when I browse for the properties
> using Enterprise Manager, the “ExchangeType 1” is not present in the Agent
> step
> 3) (Project killer) Assume I manage to set Continuous… After running the
> SqlMerge object, the status shows “initializing in progress” but it never
> finishes and I have to start again the agent from Enterprise Manager… after
> selecting Start (from Enterprise Manager) the synchronization runs as
> expected… but I cannot start it by program.
> Here are the properties and methods that I am calling after everything is
> already registered and ready:
> //set up the publisher
> m_oSqlMerge.Publisher = m_sDistServerName;
> m_oSqlMerge.PublisherSecurityMode =
> SQLMERGXLib.SECURITY_TYPE.DB_AUTHENTICATION;
> m_oSqlMerge.PublisherDatabase = m_sDbName;
> m_oSqlMerge.PublisherPassword = m_sDistPassword;
> m_oSqlMerge.PublisherLogin = "sa";
> m_oSqlMerge.Publication = m_sDbName;
> //set up the distributor
> m_oSqlMerge.Distributor = m_sDistServerName;
> m_oSqlMerge.DistributorSecurityMode =
> SQLMERGXLib.SECURITY_TYPE.NT_AUTHENTICATION;
>
> //set up the subscriber
> m_oSqlMerge.Subscriber = oSub.ServerName;
> m_oSqlMerge.SubscriberDatabase = oSub.DatabaseName;
> m_oSqlMerge.SubscriberDatasourceType =
> SQLMERGXLib.DATASOURCE_TYPE.SQL_SERVER;
> m_oSqlMerge.SubscriberSecurityMode =
> SQLMERGXLib.SECURITY_TYPE.DB_AUTHENTICATION;
> m_oSqlMerge.SubscriberLogin = "sa";
> m_oSqlMerge.SubscriberPassword = sPassword;
> //set up the subscription
> m_oSqlMerge.SubscriptionType = SQLMERGXLib.SUBSCRIPTION_TYPE.PULL;
> m_oSqlMerge.SynchronizationType =
> SQLMERGXLib.SYNCHRONIZATION_TYPE.AUTOMATIC;
> m_oSqlMerge.ExchangeType = SQLMERGXLib.EXCHANGE_TYPE.UPLOAD;
> ProgressValue = 0;
> //Initialize
> m_oSqlMerge.Initialize();
> m_oSqlMerge.Run();
> //m_oSqlMerge.Terminate(); //No need to terminate if continuous
>

Programming + MSDE 2000

Hi.
I want to be able to programmatically access MSDE
databases. I would rather not use Visual Basic. My
preference would be to either access MSDE databases using
ODBC, or to use a DLL, so that I am more flexible in my
choice of programming tools. If all else fails, then I
would have to use some API (I do not use .NET, the latest
version of Visual C++ I have is 6.0, and I would rather not
have to upgrade). What are my options? Where do I get the
API, if one is necessary?
TIA,
Joseph
From classic VB, ADO is probably your best choice. ADO is a COM object, and
it comes with MDAC (I believe), which you already have on your machine
assuming you have a decently recent OS (W2K or higher). There are some ADO
newsgroups I believe, btw.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Joseph" <msde2000@.techscribe.com> wrote in message
news:18a301c4110f$ddb27be0$7d02280a@.phx.gbl...
> Hi.
> I want to be able to programmatically access MSDE
> databases. I would rather not use Visual Basic. My
> preference would be to either access MSDE databases using
> ODBC, or to use a DLL, so that I am more flexible in my
> choice of programming tools. If all else fails, then I
> would have to use some API (I do not use .NET, the latest
> version of Visual C++ I have is 6.0, and I would rather not
> have to upgrade). What are my options? Where do I get the
> API, if one is necessary?
> TIA,
> Joseph
|||"Joseph" <msde2000@.techscribe.com> wrote in message
news:18a301c4110f$ddb27be0$7d02280a@.phx.gbl...
> Hi.
> I want to be able to programmatically access MSDE
> databases. I would rather not use Visual Basic. My
> preference would be to either access MSDE databases using
> ODBC, or to use a DLL, so that I am more flexible in my
> choice of programming tools. If all else fails, then I
> would have to use some API (I do not use .NET, the latest
> version of Visual C++ I have is 6.0, and I would rather not
> have to upgrade). What are my options? Where do I get the
> API, if one is necessary?
> TIA,
> Joseph
As you mention C++ and VB 6, I'll assume you're doing Windows apps?
There are MFC classes that support database access, since you say you'd
prefer not to use VB.
CDatabase, CRecordset, etc are what you want.
Peter [MVP Academic]
|||MSDE 2000 supports the same API set as the database engine in the other
versions of SQL Server 2000:
ADO.NET using the SQLClient namespace.
ADO and OLE DB using the SQLOLEDB provider
ODBC using the SQL Server ODBC Driver.
For more information, see this topic in the latest update to the SQL Server
2000 Books Online:
http://msdn.microsoft.com/library/?u...asp?frame=true
You can also download the latest version of the Books Online from this
location:
http://www.microsoft.com/sql/techinf...2000/books.asp
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights