Creating a shared ODBC dsn for Access to SQL Server connection

I have a Microsoft Access application which uses linked SQL Server tables. I would like to create an ODBC DSN which would be available to all users so that I don't have to create a DSN on each machine. Can this be done? The Access application resides on a shared drive (Windows). Thanks for your help.

Don,

Will a File DSN work for what you are trying to do? I don't have much experience with those, so I can't help you more in that area.

I too had a similar problem as you do, and I didn't want to go through manually creating a DSN on everybody's machine. I found this script that will make your life slightly easier:

http://www.enterpriseitplanet.com/resources/scripts_win/article.php/3089341

With a little modification to the example included in that web page, I had all my users that needed a DSN ready to rock within a mouse-click!

Thanks,

Chuck

|||Thanks, Chuck. The script will certainly make the process easier if there isn't a way to create a global ODBC DSN. Appreciate the help.

CreateSubscription with a shared schedule

In BOL I read that The valid values for the EventType argument of CreateSubscription are TimedSubscription or SnapshotUpdated.
What if I want to use an existing shared schedule, which in the reportserver database appears as type SharedSchedule? Do I still use TimedSubscription?
And how can I serialize the schedule object in order to get the xml used in CreateSubscription attribute MatchData?
In other words, how do I use an existing shared schedule with CreateSubscription? Are there any other examples, apart from the one in BOL?Try to send the SbuscriptionID of your shared schedule in the matchdata
parameter (without any XML tag)
"vsiat" <vsiat@.discussions.microsoft.com> a écrit dans le message de
news:EF725471-5320-444D-9144-5305E10ADC07@.microsoft.com...
> In BOL I read that The valid values for the EventType argument of
CreateSubscription are TimedSubscription or SnapshotUpdated.
> What if I want to use an existing shared schedule, which in the
reportserver database appears as type SharedSchedule? Do I still use
TimedSubscription?
> And how can I serialize the schedule object in order to get the xml used
in CreateSubscription attribute MatchData?
> In other words, how do I use an existing shared schedule with
CreateSubscription? Are there any other examples, apart from the one in BOL?
>|||For a subscription to use a shared schedule, pass in TimedSubscription for
the eventType and the schedule ID for the match data. You can get the
schedule ID by calling listSchedules.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart@._A_hAotmail_A_.com> wrote in message
news:OL8Xs1dXEHA.1048@.tk2msftngp13.phx.gbl...
> Try to send the SbuscriptionID of your shared schedule in the matchdata
> parameter (without any XML tag)
>
> "vsiat" <vsiat@.discussions.microsoft.com> a écrit dans le message de
> news:EF725471-5320-444D-9144-5305E10ADC07@.microsoft.com...
> > In BOL I read that The valid values for the EventType argument of
> CreateSubscription are TimedSubscription or SnapshotUpdated.
> >
> > What if I want to use an existing shared schedule, which in the
> reportserver database appears as type SharedSchedule? Do I still use
> TimedSubscription?
> >
> > And how can I serialize the schedule object in order to get the xml used
> in CreateSubscription attribute MatchData?
> >
> > In other words, how do I use an existing shared schedule with
> CreateSubscription? Are there any other examples, apart from the one in
BOL?
> >
>