Great, thanks.
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Sam
>
> Your assumption is correct. The developer will need an SQL login and VPN access to the network that it is on. YOur IT guys can set up the user with what he needs.
>
> Bill
>
> --- In MS_Access_Professionals@yahoogroups.com, "sarmbraugh" <sarmbraugh@> wrote:
> >
> > Thanks Bill. Tried the IP address but got the same error message unfortunately. I ended up just exporting each table and adding keys, indexes and relationships manually so maybe it doesn't matter so much although probably good to figure out at some point.
> >
> > Actually I have a question that might be related. There is an offsite developer who needs to do some work with this database, but I think the SQL Server is on the intranet -- assuming this is true because I can only access it via SQL Server authentication onsite, does that make sense?
> >
> > I'm not sure how to handle that or if there's something I should ask the IT department for to give the offsite person access. VPN?
> >
> > Sam
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> > >
> > > Sam
> > >
> > > You're welcome. Maybe you can use the IP address instead of the SQL Server name.
> > >
> > > Bill
> > >
> >
>
Tidak ada komentar:
Posting Komentar