If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Input problem with textbox
Hello,
One particular machine is having a problem with inputing a text field with an input mask, !\(999") "000\-0000;;* Rather than filling in the textbox, the cursor stays in its position and the numbers change in that position as the user types. I am not sure when this began, but it wasn't always that way on that machine. I tested by taking the input mask off, so that is definately the problem. Thanks for any help and God Bless, Mark A. Sma |
#2
|
|||
|
|||
Input problem with textbox
Does each computer have its own front-end file? If not, it should. Next, try
copying the front-end file from a computer where it's working properly to the computer that has the problem. I suspect the textbox is corrupted. If so, replacing the file with a working one should solve the problem. -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... Hello, One particular machine is having a problem with inputing a text field with an input mask, !\(999") "000\-0000;;* Rather than filling in the textbox, the cursor stays in its position and the numbers change in that position as the user types. I am not sure when this began, but it wasn't always that way on that machine. I tested by taking the input mask off, so that is definately the problem. Thanks for any help and God Bless, Mark A. Sma |
#3
|
|||
|
|||
Input problem with textbox
Wayne,
All users share a common .mde from the server. I tested for a corrupted textbox. There are three phone fields with the same input mask acting the same. I removed the input mask from one of the textboxes, and added a new textbox with the input mask. The old textbox with the input mask removed was fine, but the new textbox with the input box added was a problem. I tested this with a new .mde as well as a copy of the .mdb I lso tried your suggestion of moving the front end onto the local drive, which didn't help. I would like to try uninstalling and reinstalling Access, but this company has disks all over the place and I don't know which Office CD goes with that machine. I am hoping someone recognized the problem and has another solution. God Bless, Mark "Wayne Morgan" wrote in message ... Does each computer have its own front-end file? If not, it should. Next, try copying the front-end file from a computer where it's working properly to the computer that has the problem. I suspect the textbox is corrupted. If so, replacing the file with a working one should solve the problem. -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... Hello, One particular machine is having a problem with inputing a text field with an input mask, !\(999") "000\-0000;;* Rather than filling in the textbox, the cursor stays in its position and the numbers change in that position as the user types. I am not sure when this began, but it wasn't always that way on that machine. I tested by taking the input mask off, so that is definately the problem. Thanks for any help and God Bless, Mark A. Sma |
#4
|
|||
|
|||
Input problem with textbox
Does it do it on your local computer where you're creating the mde file?
Does it do it on all client computers? Do you have an input mask defined in the table and in the control, if so, are they the same or different? Is there any code that runs (such as in the control's Change event) as you make the entry that may be interfering? -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... Wayne, All users share a common .mde from the server. I tested for a corrupted textbox. There are three phone fields with the same input mask acting the same. I removed the input mask from one of the textboxes, and added a new textbox with the input mask. The old textbox with the input mask removed was fine, but the new textbox with the input box added was a problem. I tested this with a new .mde as well as a copy of the .mdb I lso tried your suggestion of moving the front end onto the local drive, which didn't help. I would like to try uninstalling and reinstalling Access, but this company has disks all over the place and I don't know which Office CD goes with that machine. I am hoping someone recognized the problem and has another solution. God Bless, Mark "Wayne Morgan" wrote in message ... Does each computer have its own front-end file? If not, it should. Next, try copying the front-end file from a computer where it's working properly to the computer that has the problem. I suspect the textbox is corrupted. If so, replacing the file with a working one should solve the problem. -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... Hello, One particular machine is having a problem with inputing a text field with an input mask, !\(999") "000\-0000;;* Rather than filling in the textbox, the cursor stays in its position and the numbers change in that position as the user types. I am not sure when this began, but it wasn't always that way on that machine. I tested by taking the input mask off, so that is definately the problem. Thanks for any help and God Bless, Mark A. Sma |
#5
|
|||
|
|||
Input problem with textbox
"Wayne Morgan" wrote in message ... Does it do it on your local computer where you're creating the mde file? No, I never have problems on my Dev machine, but myriads of problems on user machines in varous applications. Does it do it on all client computers? No only on one machine. Do you have an input mask defined in the table and in the control, if so, are they the same or different? Yes its the same in both places, but its a good point. I will try removing it later when the users are off and see if it solves it. Is there any code that runs (such as in the control's Change event) as you make the entry that may be interfering? No, but another good point |
#6
|
|||
|
|||
Input problem with textbox
For it to only happen on one machine, would normally be a bad install or
something wrong with the References, but I don't know if a References problem would affect an input mask. It may be worth looking at though, just to make sure. For information on this, see http://www.allenbrowne.com/ser-38.html. I would also verify that the current video driver is installed for that computer and that all Office and Jet patches have been installed. -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... "Wayne Morgan" wrote in message ... Does it do it on your local computer where you're creating the mde file? No, I never have problems on my Dev machine, but myriads of problems on user machines in varous applications. Does it do it on all client computers? No only on one machine. Do you have an input mask defined in the table and in the control, if so, are they the same or different? Yes its the same in both places, but its a good point. I will try removing it later when the users are off and see if it solves it. Is there any code that runs (such as in the control's Change event) as you make the entry that may be interfering? No, but another good point |
#7
|
|||
|
|||
Input problem with textbox
Wayne,
This hasn't always been a problem on this machine. I only heard about it recently and the machine is a couple of years old. As far as patches, I don't get involved with these machines to that extent, so I don't if thats that case. When I tried installing Windows SP2 on my computer it blew it away, so I won't ever tried to update someone else machine with patches. I'll just write this one up as another Microsoft folly...lol. God Bless, Mark "Wayne Morgan" wrote in message ... For it to only happen on one machine, would normally be a bad install or something wrong with the References, but I don't know if a References problem would affect an input mask. It may be worth looking at though, just to make sure. For information on this, see http://www.allenbrowne.com/ser-38.html. I would also verify that the current video driver is installed for that computer and that all Office and Jet patches have been installed. -- Wayne Morgan MS Access MVP "Mark A. Sam" wrote in message ... "Wayne Morgan" wrote in message ... Does it do it on your local computer where you're creating the mde file? No, I never have problems on my Dev machine, but myriads of problems on user machines in varous applications. Does it do it on all client computers? No only on one machine. Do you have an input mask defined in the table and in the control, if so, are they the same or different? Yes its the same in both places, but its a good point. I will try removing it later when the users are off and see if it solves it. Is there any code that runs (such as in the control's Change event) as you make the entry that may be interfering? No, but another good point |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Query Where Clause | Charles G via AccessMonster.com | New Users | 5 | September 22nd, 2005 01:15 PM |
Problem with Textbox formatting | melgarza | Powerpoint | 0 | July 8th, 2005 10:53 PM |
Major Input Problem | DS | General Discussion | 9 | February 15th, 2005 08:15 PM |
XL2003 Validation Input Msg Problem | Phil | General Discussion | 3 | July 28th, 2004 02:43 AM |
Productkey problem when installing office 2003 on network | Stefan Schreurs | Setup, Installing & Configuration | 1 | June 1st, 2004 11:16 PM |