Scheduling / Rental - Its a lot to ask, but I do need the help Tha

[TexasDon]

I overextended myself. I am creating a database for a small office that rents
a pretty narrow range of items by the day.

I saw the wizzards, resource mgt, customer service, etc, and it seemed like
they all covered my needs: work order, reserve, rent, bill, and inventory.

Can I use each wizzard for each portion, then try and link them all in the
end? Should I start from scratch?

 

[iam]

I overextended myself. I am creating a database for a small office that rents
a pretty narrow range of items by the day.

I saw the wizzards, resource mgt, customer service, etc, and it seemed like
they all covered my needs: work order, reserve, rent, bill, and inventory.

Can I use each wizzard for each portion, then try and link them all in the
end? Should I start from scratch?

Depends on how close the wizzard is to your final project needs

AND

how good you are at combining predone materials.

My bet is it will drive you nuts.

Did you already bid the project?

You'll make more if you code it from scratch.

Willing to collaborate?

I am sure many here would love a piece of the project.

 

[gulfloves]

I've been using data bases in microsoft works 7.0 as far as keeping track of
daily rentals and also long term rentals. It took me a while to figure it
out but it is fairly simple compared to 'office 2003'. I've just started
with office and don't quite know the ins and outs of it yet but if someone
could be of some help I would apprciate it as well. If you would like to see
what I've got in Works 7.0 let me know. It is nothing like the set up that
you have ot go through in office.

 

[Allen Browne]

The wizard-generated databases are really nothing more than sample ideas.
They are not robust enough for every-day use. By all means, glean ideas from
them - particularly Relationships on the Tools menu, which will give you
some idea of how to relate what to what.

The basic tables will be like this:

- Customer table: one record for each person/company who hires things.

- ItemType: one record for each category of thing you rent, e.g. TV,
radio, fridge.

- Item: one record for each instance of an item. Example: the TV with serial
number xxxx.

- Rental: one record for each time a customer rents some things. Fields:
o RentalID AutoNumber primary key
o RentDate Date/Time date this was taken out.
o CustomerID Number foreign key to Customer.CustomerID

- RentalDetail: one record for each Item in a rental. Fields:
o RentalDetailID AutoNumber primary key
o RentalID Number foreign key to Rental.RentalID.
What this is part of.
o ItemID Number foreign key to Item.ItemID.
What was rented.
o DueDate Date/Time date this item is due back.
o Amount Currency charge for this item.

Perhaps most rentals have only one item, but the structure above will let
you rent multiple items at one time.

 

[gulfloves]

Don , as I stated in my earlier response . I use the database format in
Microsoft works 7.0 . if you want to get up and running quickly , I would
suggest using this format . It is much simpler to use and can be an be used
in your Microsoft office program to a format that is recognized by Microsoft
office after you have had time to deal with the much more complicated
Microsoft office database . If you would like ot contact me personally you
may do so at (e-mail address removed)

 

[Allen Browne]

...Microsoft works 7.0 ... I would suggest using this format .

Troll alert.