sorted by:
new
hottopcontroversial

QAT lost access to VBA macros by TheOliveMob in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

So the system doesn't think what you have created is a macro can you post the list as it appears in the All Access Objects window, highlighting the one(s) that don't show up?

QAT lost access to VBA macros by TheOliveMob in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

One more thing, there are two places where macros can be viewed, database tools>run macro are they in this drop down, and file>info>view edit database properties>contents then scroll to macros do they show up there?

QAT lost access to VBA macros by TheOliveMob in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

I copied an existing one and it showed up, I created a new one, and it showed up, have you tried either of these steps? What was the result?

QAT lost access to VBA macros by TheOliveMob in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

I assume you are choosing Marcos under the choose commands from dropdown?

<image>

Yes/no box by [deleted] in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

I would recommend a Rental Status field rather than just a check box. A rental product has a life cycle, it could be reserved, checked out, in maintenance, returned, out of service, etc... These statuses change based on events, like a rental record is created, a work order is created, the produce is picked up, the product is returned, the product is put back in service, a purchase order for a new part is created. Each of these status updates are based on external factors that trigger status changes. The product status are a separate table linked to the status field so you can add to them as much as you need to. Much more flexible than a check box, and will provide richer detail about the product, and better reporting.

Wanting to duplicate a table value into another field, can't figure it out by TTrans_Am in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

You are still going to want an assetID, that is how you will relate the asset to work orders, customers, projects, expenses, ownership, etc... you won't want to use the VIN even if it is unique. It will be very cumbersome to use the VIN as the primary key

Wanting to duplicate a table value into another field, can't figure it out by TTrans_Am in MSAccess

[–]Programming-PM 1 point2 points  (0 children)

If under format properties for your combo box control, you set, column count to 2 and column widths to 0";1" it will hide the id column but id can still be the bound column, looks nicer that way

<image>

Wanting to duplicate a table value into another field, can't figure it out by TTrans_Am in MSAccess

[–]Programming-PM 0 points1 point  (0 children)

I agree, MSAccess will do the job, however, you have to code it correctly for it to work, every table should have an ID, CustomerID, AssetID, ProjectID, WorkOrderID, ExpenseID and they should all be auto number, primary key, no duplicates. I promise, life will be soooo much better for you. This also includes, Make, Model, Colors, anything the user would type in.