solutions wanted Help with lending library, equipment rental software

[milo1985]

Hello, if anyone could help me with this I would greatly appreciate it.

I am working on a solution for a photographic hire company, we know our competitors use a pc program that is called nx rental desk, it is very slow an convoluted. We only need something very simple, for instance it doesn't have to hold details of the equipment' rental cost or vat as this is done in our accounting software.

So having looked at some solutions it appears the fmp9's very own "lending library" is very close, though there is one huge flaw and that is that it doesn't let you prebook and item, you can only check out a piece of equipment using todays date. We only have a small amount of equipment so we will regularly book it in for numerous shoot dates up to about 2 weeks in the future.

So my questions is - does anyone know how to adjust "lending library" so that you can prebook equipment out for numerous dates in the future.

Thank you!!!

Milo

[Fenton]

I think the only thing you need to do is to put those fields on the layout, "Process Check Out", which is a History table layout. He/she has preset the fields to the current date and time. Which is fine, but by not putting them on the layout, they've limited your ability to edit them.

Otherwise the script can run much as is. I would change the placement of the Commit Records step. I think it should be AFTER the last Set Field [ Assets::AssetID ] in the script. Otherwise they're taking you back to the original layout with the record still open. Also, as it is, if one of the message dialogs kicks in, telling a field is empty, and you enter a value, there is no Commit Record afterwards. Maybe they have some other idea about this, but I don't like it -]

There are 3 scripts named "Process Check Out" :-! Which is a little weird, IMHO. You want the 3rd one, under the ----History ---- script label.

All and all, this file was obviously converted from 6. The Custom Dialogs still say "Message" as the title of the dialog, which, while not wrong, is kind of lame.

Also, be a little cautious if you edit that script inside the Loop. The script has Allow User Abort ["Off"], then a Loop with Pause. This effectively traps you in the Loop if anything is wrong. However, if you accidentally added something, such as a test for a field that was not on the layout, or a test that always failed, you would have to Force Quit FileMaker to stop the loop. So do not work on that part while any other FileMaker files are open. It's bad for a local file if FileMaker is Force Quit. Or temporarily change it to Allow User Abort ["On"] for testing.

[Yogeshnath]

Hi Fenton,

Which fields are you referring to?

Regards,

y