What all are the features that do run in Ms Access Application. Not in Runtime? (1 Viewer)

[prabha_friend]

My client's Ms Office trial license has expired. Planning to utilize the runtime instead of purchasing the application... if it works

Private Sub SaveToPenDrive()
  Call DoCmd.OpenReport("Delivery_Weekly", acViewPreview, , "Customer=" & Me.ID.Value)
  If Dir("E:\Software Bills\" & Date & "\", vbDirectory) = "" Then MkDir ("E:\Software Bills\" & Date & "\")
  Call DoCmd.OutputTo(acOutputReport, "Delivery_Weekly", acFormatPDF, "E:\Software Bills\" & Date & "\" & Me.NameVal.Value & ".pdf")
End Sub

Thanks.
With Hope,
Prabhakaran

 

[June7]

I've never worked with Runtime but from what I understand, that posted code should still work. Code that creates/modifies objects might not work.

Don't need Call preceding DoCmd commands. Remove the parentheses.

MkDir also does not need parentheses.

 

[GPGeorge]

My client's Ms Office trial license has expired. Planning to utilize the runtime instead of purchasing the application... if it works

Private Sub SaveToPenDrive()
  Call DoCmd.OpenReport("Delivery_Weekly", acViewPreview, , "Customer=" & Me.ID.Value)
  If Dir("E:\Software Bills\" & Date & "\", vbDirectory) = "" Then MkDir ("E:\Software Bills\" & Date & "\")
  Call DoCmd.OutputTo(acOutputReport, "Delivery_Weekly", acFormatPDF, "E:\Software Bills\" & Date & "\" & Me.NameVal.Value & ".pdf")
End Sub

Thanks.
With Hope,
Prabhakaran

The runtime is, just as the name suggests, used to execute your application. That excludes the design elements found in the full version.

So, your users couldn't create new VBA procedures, to take an obvious example. I don't know if you could write code that created objects on the fly, but that doesn't seem to be something you'd be doing frequently anyway, even in a full version.

The procedure shown, on the other hand, doesn't attempt to change the Access accdb. It's probably fine in the runtime.

The best way to validate what does or doesn't work would be for you to install the runtime and use it to run the accdb in question.

However, it's important to keep in mind that your accdb will be frozen as is when you no longer have the full version installed to make any enhancements to it.

 

[Isaac]

Make sure to have good error handling in any non-trivial procedure if you are going to use runtime

 

[prabha_friend]

So. You all suspect the same? That a feature which is not running in a subscribed application may run in runtime...!

 

[June7]

So. You all suspect the same? That a feature which is not running in a subscribed application may run in runtime...!

prabha, did you put "not" in the wrong position in that statement?

 

[prabha_friend]

Sorry. Not that much good in Grammar. I failed in English classes

 

[Isaac]

generally the same 'features' work, unless, as CJ mentioned I think, you are trying to open or save things in Design view.
you have to have a tight ship - a tight app well buttoned up to be a good fit for runtime. if you have all kinds of errors here and there, it will be painful to switch

 

[Pat Hartman]

@prabha_friend If you want to test out how the Runtime works on your PC without installing it, rename the .accdb to .accdr. This tells Access to pretend to be the runtime engine. You will see that the menus change and things like print are not available. So, you may need to make modifications to compensate.

 

[prabha_friend]

@prabha_friend If you want to test out how the Runtime works on your PC without installing it, rename the .accdb to .accdr. This tells Access to pretend to be the runtime engine. You will see that the menus change and things like print are not available. So, you may need to make modifications to compensate.

Sure Pat. Thanks. Will Test and update soon.

 

[GaP42]

A gotcha that could occur with deployment of your app on PCs with just the runtime MS Access installed on the client's PC:
- it may not apply in your client's case where a trial version of office was used (as the trusted location may have been set while using it).
The access app needs to be installed in a trusted location.
However your client's, using the Access Runtime to open the app, cannot set the folder in which your app is located to be a trusted location using the runtime only.
That means a regedit is needed, or some script that sets it. Isladogs has some advice on his site about trusted locations and alternatively(?)signing of the app.

 

[prabha_friend]

A gotcha that could occur with deployment of your app on PCs with just the runtime MS Access installed on the client's PC:
- it may not apply in your client's case where a trial version of office was used (as the trusted location may have been set while using it).
The access app needs to be installed in a trusted location.
However your client's, using the Access Runtime to open the app, cannot set the folder in which your app is located to be a trusted location using the runtime only.
That means a regedit is needed, or some script that sets it. Isladogs has some advice on his site about trusted locations and alternatively(?)signing of the app.

Will update you in two days...