In his article ******** explained that the way to execute applications in a form is different depending on the application. The code he published allowed to execute the PowerShell ISE in an Access form, but not any application with that approach.
@theDBguy
It doesn't work for me. If I change the underlying image without changing its .Picture property executing a form .Refresh doesn't update the image on the screen.
To completely uninstall MS Office 365 I always use:
Uninstall Microsoft 365 from a PC
Instead of uninstalling Office 365 with the computer uninstaller.
If you want or need to change the SYMBOL_NAME description after being selected, you have to assign the value in the Symbol_Stock AfterUpdate() event:
Me.Symbol_Name = Me.Symbol_Stock.Column(1)
I don't think there are a real speed difference on most of databases. CurrentlyI install x64 on my clients but there is no real improvement on my applications.
When you call .Update on a DAO Recordset, the current record’s buffer is written to the database and may be repositioned or refreshed — depending on the recordset type and underlying query.
This means that the record you were editing might no longer be current, or DAO needs to requery to see...
@Mark has explained what the problem is. A simple way to avoid going to a new record is changing this line on your create Invoice button:
Richard Rost would be happy to see this database. ;)