Hi,
MYOB must have some way of connecting to SQL Server. So you could always
connect as that user account...
Alternatively, do as Greg Low suggests and try moving the DB to another
machine. Assuming they haven't implemented some encryption mechanism, you
should have access to the data, and you
On Sun, Aug 15, 2010 at 10:54 AM, Greg Keogh wrote:
> >Just stop the service, copy the mdf and ldf files to another place and
> > reattach them to another instance where you are admin.
>
> Hmmm! I’ll give that a bash next week when I’m back on the machine where
> it’s installed.
>
> Someone in the
>Just stop the service, copy the mdf and ldf files to another place and
reattach them to another instance where you are admin.
Hmmm! I'll give that a bash next week when I'm back on the machine where
it's installed.
Someone in the group here several weeks ago pointed out that this "security
Hi Greg,
Just stop the service, copy the mdf and ldf files to another place and
reattach them to another instance where you are admin.
Regards,
Greg
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Greg Keogh
Sent: Sunday, 15 August 2010 9:42 A
Howdy on Sunday. Who's working?
I was working last week on a machine that had a preview release of MYOB
"Huxley" on it. I think this is part of their long overdue second attempt at
using .NET. But I also think it's only the backend that uses .NET (anyone
know how their .NET development is going
