[AccessD] More hi-jinks

[Susan Harkins]

>
>
> Look at these "hi-jinks" this way.  You probably wound up with this
> "simple" database problem because somebody on the [paid] full time IT staff
> with the State of Kentucky was assigned the task, spent a little time going
> around in circles and then gave up reporting back to their [incompetent]
> bosses that what they wanted "... couldn't be done" and that was that.
>

=========No, it isn't a priority. Our IT staff has 4 people -- to support
an entire state agency. It just isn't a priority and will never get done if
left to IT. Now, here's the kicker -- software already exists and it does
everything we need, but the agency won't pay for it because, "We have IT
staff for that..." -- seriously... that's what they said. But, if IT even
put it on their list, it would be years... if ever. Rock and a hard place.
So, I volunteered. At the least, it's keeping some synapses firing, and
it's ... coloring and puzzles would bore me to tears.

>
>
> So how does all this apply to you and Salato?  Susan, you should look at
> this as an opportunity to excel!  Solve this problem and you could wind up
> getting promoted into a full time state job (with full benefits) and all
> that.  Heck, if there are other Salato offices spread around the state, and
> your software is really good, you could wind up with a big promotion as you
> will be seen as indispensable - your solution could wind up being used in
> every single Salato location.  Susan Harkins of Frankfurt, Kentucky will
> suddenly be a programming superstar!  (You'll be Wonder Woman!)
>

=========Thank you for the nice vote of confidence, but I don't want a
promotion. :) There's only one Salato. :) I'll never be a programming
superstar, but thank you. :)

>
> Just think: This is not an unsolvable problem - this is an opportunity to
> excel!  Plus you have a crack team of free "consultants" to help you.
> (that would be us ...)  :-))
>

=========Yes, and you've saved my butt on a number of occasions. :)

Thank you all!

Susan H.

>
>
>
>
>
> Quoting FW Salato Center <Salato at ky.gov>:
>
> Just when I thought I had this thing mastered - I will never volunteer to
>> write another simple database. ;)
>>
>> I think you all know the main problem - the distinction between
>> individuals and species tasks. With the medical/vaccine, I provided a
>> second form for species and used a Recordset to update all animals of the
>> same species when tested, vaccinated, and so on. The form displays a list
>> of individuals in that species and the user can remove an individual. We
>> can also update an individual within that species as necessary, and it
>> often is. We have one bison cow that receives a lot of specialized care
>> that the others don't need.
>>
>> New complication - food. We've just started working on the food structure
>> - the longer I chew, the bigger it grows. :(
>>
>> Food for the individual animals is easy to track - amount in, amount
>> removed from previous feeding. These animals are all fed as individuals.
>>
>> We have several species that are fed as a group. There's no way to divvy
>> up that feed by individual, so the medical/vaccine solution or specifying a
>> vaccine or treatment and updating all of the animals in that species
>> doesn't work. I can't update each individual because there's no way to
>> track how much each individual ate on a given day, if any at all. The herd
>> or flock is fed and I can track the herd, but there is no "herd" or "flock"
>> entity for these species. They're all identified as individuals, because we
>> need them ided that way. As I mentioned before, we have a bison cow that
>> needs medical care that none of the others do (and she often does). They
>> need individual status.
>>
>> I'm seriously considering just throwing in an entity called "deer stock,"
>> "bison stock," "turkey stock" - and so on. Perhaps I need a second table of
>> herd/flock types and then I can always use a UNION when I need to combine
>> individuals and groups for some reason. That probably complicates date
>> entry - but I'm using multiple data entry forms for individual/stock
>> conflicts, so that's not really all that new.
>>
>> I just have no idea where this is going to lead at the moment.
>>
>> I should be home knitting and dividing flowers in my yard.
>>
>> Susan H.
>>
>>
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>