Search results

Hi Barbara No attachment

Hi Barbara Can you upload the Db so we can see the problem?

True, badly worded on my part. Probably best to say that you cannot set the relationship unless bad data is removed.

True but the purpose of the Post was to indicate to the OP what the error was.

Hi Attached is a screenshot of what I think are the required Relationships. Not all tables are as yet included.

Hi Can you send me your current "tblMachine" with actual data?

When you talk about Machine ID 312 and 1046, are these ID numbers that have been Manually created by you?

No it makes complete sense

Hi You must have a specific List of PayRangeDevices which are installed into a specific Machine. Then depending on circumstances the Device has to be removed from 1 machine and placed into another. Can you give me an example list of current PayRangeDevices?

Hi Can you give me an example list of the "PayRangePin" you use ?

OK but your current tblMachineInventory does not even have a field for MachineID ?

Hi What specific details do you record about a Machine? Do you have specific Serial Numbers or other details other than a MachineID ?

Thanks for that. Are there specific Locations you install Machines in a Property?

Can you give us a list of Machine Types you install ?

Hi Can you explain the use of "tblPayRangeAssignment" ?

What are the various "Types" of Properties that you install Machines in?

Can you upload a copy of your database?

Upload the database so we can see what you mean.

Your sample database has a few problems in table design. 1. Product Table Product_Actual_ID PK set as Text - It is recommended that the PK be set as an Autonumber - LongInteger Datatype Category field set as a Lookup - You should not use Lookup Fields in Tables 2. StockIn Table StockIn field...

Hi Pat Yes. Also the fact that fields in tables which were supposed to be numeric were in fact text due to Import from an Excel file.