What language are you using?  Can you show your declaration?

VBA in an access application

here is where I get the error message if I try to late bind the application

Dim CPTIMECARD1header As AccpacCOMAPI.AccpacView

I tried to DIM AccpacCOMAPI.AccpacView as Object but this failed

64-bit Access won't work

I'm using 32 bit.  I cannot compile my sub-routine unless I have COMAPI referenced but not all users have COMAPI so I have to un-reference it to have the Access app work.  I thought late binding would help me compile the sub-routine so I could put some code in to attach the reference.  Is there a better way to do this?

The Sage client must be installed, i.e., WSSETUP, to use the COMAPI.

What is the error message?  You should be able to do this.

If I'm reading your post above correctly, you're trying to re-declare AccpacCOMAPI.AccpacView as Object - you can't do that in VBA.

You want:

Dim CPTIMECARD1header As Object

I tried the following DIM CPTIMECARDheader1 as Object but later when I started to add timesheets to Sage the Dim CPTIMECARDheader1 as AccpacCOMAPI.AccpacView erred out with User-defined type not defined.  Is it just possible to register COMAPI or are there other dependencies?

All AccpacCOMAPI.AccpacView declarations need to be changed to As Object.  That also includes your Session object and your DBLink objects.

They will still all work even when declared as Object because of how they are created.

Declaring everything as an object got passed the compiler but this line developed an error

Set mDBLinkCmpRW = Acsession.OpenDBLink(DBLINK_COMPANY, dblink_flg_readwrite)

Run-time error '13' type mismatch.  The variable dblink were all defined as objects.

Make sure that DBLINK_COMPANY and dblink_flg_readwrite are both declared.  Those should have been within the ComAPI.  If they aren't declared, make sure that you have Option Explicit at the top of all of your code modules. You don't want to let anything be undeclared.

Yes all of those are defined as objects DBLINK_COMPANY, DBLINK_SYSTEM AND dblink_flg_readwrite.  This allows the sub-routine to compile but when I execute the following code the system errors out Run-time error '13" type mismatch.  Set mDBLinkCmpRW = Acsession.OpenDBLink(DBLINK_COMPANY, dblink_flg_readwrite)
Set mDBLinkSysRW = Acsession.OpenDBLink(DBLINK_SYSTEM, dblink_flg_readwrite). 

MdblinkCmpRW and mDBlinksysRW are defined as objects.

For some background, COMAPI is not active until some code in the sub activates it, but this is before setting up the session.  If I activate COMAPI, do not declare the dblink as objects, the sub compiles and runs.  Any way around this.  Option explicit is on.

Why can't you install Wssetup?  You do know that the COMAPI requires a user license, you can't bypass that.

DBLINK_COMPANY, etc, are just integers.  Don't define those as objects.

I defined them as integers, the sub compiles and it moves past the previous errors logging on the sage database.  But I'm getting an error when I try to compose the views for timecard entry.   These were all defined as objects.  Jay is right - Is should just do wssetup but I'm trying to be stupidly elegant and save the user from having to setup a bunch of workstations.

I defined them as integers, the sub compiles and it moves past the previous errors logging on the sage database.  But I'm getting an error when I try to compose the views for timecard entry.   These were all defined as objects.  Jay is right - Is should just do wssetup but I'm trying to be stupidly elegant and save the user from having to setup a bunch of workstations.

I've gone down that path before, too.  WSSetup doesn't take long and is fairly lightweight.  Good luck!

Many thanks to both you and Jay - I'm honoured that you would respond to me