Networks

Yes, they are routers and they are behind a main router. If I had any control over what they purchased it would have been nice. It would be great to not have to fix other peoples stuff. We can't use static IP's because both routers are in seperate buildings and provide access for the community meetings as well as the one in City Hall being used for City Manager's laptop. (That could be locked static but he travels with it as well)

you can have 1 DHCP server and use a superscope

here is a MS Technet article on superscopes.
while this is for W2008 server the principles are the same for W2003 and lower.

A wireless router is just an Access Point and a router in one box.

An AP is a mac-layer bridge, so any wireless workstations will use whatever DHCP server is on the wired network.

To make a router into an AP, just turn off DHCP and connect one of the LAN ports into the existing LAN. Set a static IP address within the same IP range of the LAN so you can get to the web config page of the unit.

Assuming that there is a Cisco router or Microsoft server on the network, use that for DHCP. Microsoft's DHCP server is fairly easy to setup, and you can do fancy things like superscoping, etc.

then simply create subnets. If users must traverse the subnets, then using routers, expecially consumer level routers is not the way to go. That's because users traversing routers do so as remote access clients (through PPTP or L2TP or other remote methods. To gain access to the LAN must have a local address. That requires DHCP relay agent and consumer level routers typically don't have that capability.

So as robo_dev mentions, simply bypass the routing function by only using the routers built in switch [and not the WAN port].