I am going to post the most annoying behavior lately from Alpha 5 here and then post other stupid error messages in a separate post. So, here goes with the #1 Annoyance:
Because of the #2 Annoyance (described separately) in my application, I went into the operations tab to create a totally new import operation that I could access from a script. I also follow this one up with an append operation. Basically, in the times past, Excel 2007 I think it was, would of allowed you to create a DBF file directly from within Excel itself. When we started with 2010, this feature of Excel went away so I had to divide my operation into an import first from an XLSX file created by Excel 2010 and then do a separate append operation once the dbf file was created. Ok, so that worked as long as we were on Windows 7 and Excel 2010.
Now here we are with Excel 2016 running on Windows 10. We had previously updated from Alpha 5 v10.5 to Alpha 5 v11, avoiding the Alpha Anywhere product because of the extremely high cost of Alpha anywhere. So, when my old import operation refused to work because of part of the #2 annoyance, I started from scratch and used xls instead of xlsx, because xlsx now refuses to work when created from Excel 2016. When I run the import operation, I start getting dialogue boxes with the message "Table Not Found" ..Local\Temp\xyz.dbf, 0 records will be imported. Then, you click ok, then it runs the operation. Why does it insist on looking first in my app\local folder for this dbf file in the first place and giving me this idiot message about 0 records being importing, and then it imports it from where it is supposed to after you click ok. I am trying to eliminate all the idiot messages because I don't want my user seeing confusing dialogues like this. So how do I stop this behavior?
Import Operation.JPG
Because of the #2 Annoyance (described separately) in my application, I went into the operations tab to create a totally new import operation that I could access from a script. I also follow this one up with an append operation. Basically, in the times past, Excel 2007 I think it was, would of allowed you to create a DBF file directly from within Excel itself. When we started with 2010, this feature of Excel went away so I had to divide my operation into an import first from an XLSX file created by Excel 2010 and then do a separate append operation once the dbf file was created. Ok, so that worked as long as we were on Windows 7 and Excel 2010.
Now here we are with Excel 2016 running on Windows 10. We had previously updated from Alpha 5 v10.5 to Alpha 5 v11, avoiding the Alpha Anywhere product because of the extremely high cost of Alpha anywhere. So, when my old import operation refused to work because of part of the #2 annoyance, I started from scratch and used xls instead of xlsx, because xlsx now refuses to work when created from Excel 2016. When I run the import operation, I start getting dialogue boxes with the message "Table Not Found" ..Local\Temp\xyz.dbf, 0 records will be imported. Then, you click ok, then it runs the operation. Why does it insist on looking first in my app\local folder for this dbf file in the first place and giving me this idiot message about 0 records being importing, and then it imports it from where it is supposed to after you click ok. I am trying to eliminate all the idiot messages because I don't want my user seeing confusing dialogues like this. So how do I stop this behavior?
Import Operation.JPG
Comment