A couple of questions....

Hello everyone,

I have a couple of questions really quick questions.

I am creating a dispatch database. What I would really like to do is
have to option of automatically inserting the time when I hit the "]"
button. Is this possble?

Also I am trying to create a form that has the standard boxes contained
within it and I would also like to add a subform or something simular in
a spreadsheet format that can be used to also enter information and to
look up information that has been entered. Would this be possable? And
if it is possable is there a way if I selected a row of infomation that
it would bring it back up in the original form?

Thanks again for your help,

Ron


--
Ron
------------------------------------------------------------------------
Ron's Profile: http://www.dbtalk.net/m48
View this thread: http://www.dbtalk.net/t296320

re: A couple of questions....

Ron wrote:[color=blue]
> Hello everyone,
>
> I have a couple of questions really quick questions.
>
> I am creating a dispatch database. What I would really like to do is
> have to option of automatically inserting the time when I hit the "]"
> button. Is this possble?[/color]

If you want to do this throughout the form, open up the forms property
sheet and open the event for OnKeyPress. Also set KeyPreview to True/Yes.

If it's for a specific field, put in an event for OnKeyPress. You can
also use OnKeyDown/Up too.

You need to find out the value for KeyAscii or KeyCode, depending on
which one you use, for the value pressed. You could enter something like
Msgbox "KeyAscii is " & KeyAscii
and find the value for ]

Then you know the value to check for to set the time. Press the F1 key
in the events I listed.
[color=blue]
>
> Also I am trying to create a form that has the standard boxes contained
> within it and I would also like to add a subform or something simular in
> a spreadsheet format that can be used to also enter information and to
> look up information that has been entered.[/color]

Yes. You are only limited by your imagination.

Would this be possable? And[color=blue]
> if it is possable is there a way if I selected a row of infomation that
> it would bring it back up in the original form?[/color]

Why would you do that if it is a subform? Anyway, you could use an
OnDblClick event to do whatever if that helps.
[color=blue]
>
> Thanks again for your help,
>
> Ron
>
>[/color]

re: A couple of questions....

Salad Thankyou for your help, you have no clue how much it is
appreciated.

As far as the form is concerned, this is what I am trying to do.

1) Some of the dispatchers that I work with like using a traditional
form with boxes and some of them like using a spread sheet format. This
is one of the reasons for both.

2) The second reason that I would like a traditional form and a
spreadsheet format of all the calls entered is to be able create a
quicker way of looking up past calls without having to click through to
entry arrows at the bottom or going over to the original table.

This is primarely becuase we have differant officers arriving and
clearing at differant times and most of the time we have additional
time(s) or clearance times/deposition codes that we need to added to
the original call. So just being able to scroll down to that particular
call to plug in any of that information what save a tremendious amout of
time for our dispatcher.

I hope this gives you a little understanding of what I am trying to do
with this particular form.

Maybe I was wrong in calling it a subform.

What would I have to do after I create the original form to add a
history of all the calls in spreadsheet format at the bottom for what I
want to do?

Thankyou everyone again for your help, it is greatly appreciated. I
hope that I am not to much of a pain.

Ron


--
Ron
------------------------------------------------------------------------
Ron's Profile: http://www.dbtalk.net/m48
View this thread: http://www.dbtalk.net/t296320

re: A couple of questions....

Ron wrote:[color=blue]
> Salad Thankyou for your help, you have no clue how much it is
> appreciated.
>
> As far as the form is concerned, this is what I am trying to do.
>
> 1) Some of the dispatchers that I work with like using a traditional
> form with boxes and some of them like using a spread sheet format. This
> is one of the reasons for both.
>
> 2) The second reason that I would like a traditional form and a
> spreadsheet format of all the calls entered is to be able create a
> quicker way of looking up past calls without having to click through to
> entry arrows at the bottom or going over to the original table.
>
> This is primarely becuase we have differant officers arriving and
> clearing at differant times and most of the time we have additional
> time(s) or clearance times/deposition codes that we need to added to
> the original call. So just being able to scroll down to that particular
> call to plug in any of that information what save a tremendious amout of
> time for our dispatcher.
>
> I hope this gives you a little understanding of what I am trying to do
> with this particular form.
>
> Maybe I was wrong in calling it a subform.
>
> What would I have to do after I create the original form to add a
> history of all the calls in spreadsheet format at the bottom for what I
> want to do?
>
> Thankyou everyone again for your help, it is greatly appreciated. I
> hope that I am not to much of a pain.
>
> Ron[/color]

Here is something I have done, if I understand your question. This
works for me and would incorporate both single form and something
similar to a datasheet. You would need to be able to code in VBA to use
what I do. I'll use an order form as an example.

I create, via the design wizard, a form to display the orders as a
continuous form. I'll call it OrderLog. Let's say the fields are
OrderNo, DateOfOrder, CustomerName, CustomerAddress, etc. I set this
form to no edit/delete/add as I don't want to change the data in the
continuous form. I display the records sorted from most recent order to
first order.

In the Form Header I have text boxes above each column to search for an
item. So if the person puts the cursor in the FindOrderNo text box, the
op enteres the order number and the AfterUpdate event finds the order
and moves to it. Or the person could go to client and enter "Peter" It
will then find the first Peter and by pressing F3 go to the next Peter.
This is by using FindFirst/FindNext "CustomerName Like *Peter*" IOW,
it's easy to find a record if you know what to look for.

In the form header I also may have combo boxes/option groups, etc to
filter the data. For example, I may have a combo that selects all of
the salesman that have created an order. I then select from that list
"Joe Blow" and all of the sales for JoeBlow are displayed (using
Me.Filter = "Salesman = 'Joe blow'", Me.FilterOn = True. Or perhaps
Me.Filter = "Active = True", Me.FilterOn = True to display only active
orders.

In the form footer I have command buttons to add an order or goto order,
sort the list, exit, etc.

I create a function called GoToRecord. I then hilight all columns and
pull up a property sheet and enter =GoToRecord() in the DblClick event
for the fields.

So, the user can dbl-click on each row or press the GoToRecord command
button. This opens the OrderForm. When I open that form it filters the
form to the filter in the OrderLog and its sort. I then find the record
I was on in OrderLog. Now the user is in a single order form with all
of it's info for input. Since the form is filtered to that of the
orderlist, one can navigate record by record through the orders. Once
the person is finished with a single order, he presses the exit button.
It gets the current order number and if the order log is open, finds
the current order number in the log and closes the order form. This way
the two forms remain synchronized.

Once you have created a log form, it's quite easy to modify it for other
logs. This is quick and easy for the ops to use. They can find records
fast and get to the record fast.

I don't know if this will meet your situation, but if works in mine.


The