distributing software

18 Jun 2009 5:01 AM

Jack Russell

I thought that one of the basics of .net was that you could just "xcopy"
the finished software to another machine provided it had the .net framework.

I have a program which I converted from vb6. It uses an access style
database (.mdb).

If I copy this and interopdao.dll to another PC that PC cannot open the DB.

Any ideas gratefully received

Thanks
-

18 Jun 2009 10:56 AM

Family Tree Mike

Show quote Hide quote

"Jack Russell" <ja***@norubbish.tpg.com.au> wrote in message
news:OfVnlH97JHA.1372@TK2MSFTNGP05.phx.gbl...
>I thought that one of the basics of .net was that you could just "xcopy"
>the finished software to another machine provided it had the .net
>framework.
>
> I have a program which I converted from vb6. It uses an access style
> database (.mdb).
>
> If I copy this and interopdao.dll to another PC that PC cannot open the
> DB.
>
> Any ideas gratefully received
>
> Thanks
> -

1. You need the .net framework version you are targeting. It sounds like
that is there, otherwise the application would not start.
2. You need the drivers for the db. Access style databases don't exist for
64 bit OSs. A work arround for that issue is to build for 32 bit OSs. To
help with your issue, you need to include what the actual error is, as well
as perhaps the lines of code that give the error.

--
Mike

18 Jun 2009 9:32 PM

Jack Russell

Code is
       On Error Resume Next
         trainmake = DAODBEngine_definst.OpenDatabase(traindb)
         If trainmake Is Nothing Then MsgBox("Could not open Database "
& traindb)
         If Err.Number <> 0 Then
             MsgBox("Error during open:" & Err.Number & "/" &
ErrorToString(Err.Number))
             Stop
         End If

I get error 5 , procedure call or argument is not valid

What are the drivers that I need, I did not have to disribute anything
with VB. Indeed the PC did not even need access installed

Thanks
Jack Russell

Family Tree Mike wrote:
Show quoteHide quote

> "Jack Russell" <ja***@norubbish.tpg.com.au> wrote in message
> news:OfVnlH97JHA.1372@TK2MSFTNGP05.phx.gbl...
>> I thought that one of the basics of .net was that you could just
>> "xcopy" the finished software to another machine provided it had the
>> .net framework.
>>
>> I have a program which I converted from vb6. It uses an access style
>> database (.mdb).
>>
>> If I copy this and interopdao.dll to another PC that PC cannot open
>> the DB.
>>
>> Any ideas gratefully received
>>
>> Thanks
>> -
>
>
> 1. You need the .net framework version you are targeting. It sounds
> like that is there, otherwise the application would not start.
> 2. You need the drivers for the db. Access style databases don't exist
> for 64 bit OSs. A work arround for that issue is to build for 32 bit
> OSs. To help with your issue, you need to include what the actual error
> is, as well as perhaps the lines of code that give the error.

18 Jun 2009 1:27 PM

Cor Ligthert[MVP]

Jack,

In past it was not uncommon the sot the mdb file in the program folder, that
is not allowed anymore in Vista and Windows 7

This kind of issues have therefore not to do with xcopy but simply with
security settings

Cor

Show quoteHide quote

"Jack Russell" <ja***@norubbish.tpg.com.au> wrote in message
news:OfVnlH97JHA.1372@TK2MSFTNGP05.phx.gbl...
>I thought that one of the basics of .net was that you could just "xcopy"
>the finished software to another machine provided it had the .net
>framework.
>
> I have a program which I converted from vb6. It uses an access style
> database (.mdb).
>
> If I copy this and interopdao.dll to another PC that PC cannot open the
> DB.
>
> Any ideas gratefully received
>
> Thanks
> -

18 Jun 2009 9:23 PM

Jack Russell

Cor,

I am running XP and have put it in its own folder on the main drive
having encountered the Vista "Program files" debacle with other programs.

Jack

Cor Ligthert[MVP] wrote:
Show quoteHide quote

> Jack,
>
> In past it was not uncommon the sot the mdb file in the program folder,
> that is not allowed anymore in Vista and Windows 7
>
> This kind of issues have therefore not to do with xcopy but simply with
> security settings
>
> Cor
>
> "Jack Russell" <ja***@norubbish.tpg.com.au> wrote in message
> news:OfVnlH97JHA.1372@TK2MSFTNGP05.phx.gbl...
>> I thought that one of the basics of .net was that you could just
>> "xcopy" the finished software to another machine provided it had the
>> .net framework.
>>
>> I have a program which I converted from vb6. It uses an access style
>> database (.mdb).
>>
>> If I copy this and interopdao.dll to another PC that PC cannot open
>> the DB.
>>
>> Any ideas gratefully received
>>
>> Thanks
>> -
>

20 Jun 2009 6:14 AM

Jason Keats

Jack Russell wrote:

> I thought that one of the basics of .net was that you could just "xcopy"
> the finished software to another machine provided it had the .net
> framework.
>
> I have a program which I converted from vb6. It uses an access style
> database (.mdb).
>
> If I copy this and interopdao.dll to another PC that PC cannot open the DB.
>
> Any ideas gratefully received
>
> Thanks
> -

You are using Interop (ie, old COM DLLs) so you cannot expect to just be
able to xcopy deploy your .NET program.

You will still need to install DAO (probably Jet 4.0). Howerver, you
don't say what version of Jet/Access you're using, so we can only guess
the answer.

One place you can get the components you require (apart from Microsoft)
is: http://www.randem.com/support.html

HTH