Norbert
I just got a confirmation that this is a known bug. To prevent it, you need to save the form as text and then load it from text.
Open the Immediate Window by pressing Ctrl+G. Type this (assuming you have a form named "frmOrders" and a folder C:\MyFolder):
SaveAsText, acForm, "frmOrders", "C:\MyFolder\frm.txt"
That saves the form as a text file. Open it in NotePad and you'll see some interesting stuff.
Open your new database and go to the Immediate window again. Type:
LoadFromText, cForm, "frmOrders", "C:\MyFolder\frm.txt"
That brings the form into the database. It should maintain all properties. Hopefully, this bug will be fixed someday.
-Bill
---In MS_Access_Professionals@yahoogroups.com, <wrmosca@comcast.net> wrote :
---In MS_Access_Professionals@yahoogroups.com, <wrmosca@comcast.net> wrote :
Sorry you had such a bad experience. I'll pass this onto one of the guys I know at MS. Maybe he can at least make the Access development team aware of it.
---In MS_Access_Professionals@yahoogroups.com, <drnorbert@msn.com> wrote :
-Bill
---In MS_Access_Professionals@yahoogroups.com, <drnorbert@msn.com> wrote :
Hi Bill,
As per your suggestion I phoned MS regarding this issue.
I had a horrible experience after 2 hours of talking to 9 people who did not qualify having any experience in MS Access 2013 and they did not care about reporting bugs, also they want me to buy support for $250 for fixing their own bug.
Perhaps you have a better way to get help MS improve Access and their luck of proper support.
Much regards
Norbert
__._,_.___
Posted by: wrmosca@comcast.net
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (24) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar