cannot find my apps in the windows store - windows-store-apps

I have had some educational apps in the windows store for over 1 year. I cannot find now them when I search on app name or app keyword (such as algebra) or my own name. Strangely a few sold about a month ago, I don't know how that happened. I am using windows 10. Could that be a factor (is there a windows 10 store as distinct from the old one?) Thanks

Related

How to submit new app updates in the published app in Partner Center / Microsoft Store?

I have an MSI installer to submit it in the Partner Center or Microsoft store. I converted my MSI installer into MSIX package format using the MSIX packaging tool.
I had already an idea of how to publish my app in the MS store using this reference: https://www.advancedinstaller.com/msix-publish-microsoft-store.html
However, there's a question that comes to my mind. Once I published my application in the MS store and
What if I have new updates in my app, what are the steps how to do that?
I did some research most of the results have something to do with source code.
My preferred approach is to update the app without coding configurations.
The submission process is managed through the Microsoft Partner Center dashboard, which is a web portal that allows developers to publish applications, and manage the updates of the application to allow keeping the app up to date automatically.
Once you submit updates to a published application, the updated packages will be available on average about two hours after submission (though this can sometimes take longer, especially with larger packages). Price, screenshot, or description changes take on average 16 hours to go live. Customers will receive the updated package the next time their device looks for updates, if (automatic app updates) are turned on,
or when they trigger the update by proceeding to the Windows Store and choosing (Check for updates) on the downloads. By default, automatic updates are turned on in the Microsoft Store, so users will always use the latest version of your application.
References:
MSIX Auto Updates https://www.advancedinstaller.com/msix-auto-updates.html
Update a public app https://blogs.windows.com/windowsdeveloper/2016/05/13/publish-or-update-a-public-app-dev-center-tip-1/
Mandatory updates https://learn.microsoft.com/en-us/windows/uwp/packaging/self-install-package-updates#mandatory-package-updates
Upload app packages https://learn.microsoft.com/en-us/windows/uwp/publish/upload-app-packages

Excel 2016 Connection to MySQL in Data New Query From Database

I have a spreadsheet that was created in Excel 2010 and queries a MySQL database using Power Query. I'm trying to use the same query and connection on a new laptop with Windows 10 and Excel 2016. I know that the Power Query functionality has been rolled into the Data tab functionality. I've installed the MySQL installer and Connector/Net. However, I'm unable to see the MySQL option in when going to the Data Tab and selecting New Query From Database.
MySQL is only supported on premium SKUs of Office 2013 and 2016. This link describes the features available to premium SKUs of Office 2016 while the April 2015 section on this page lists the data sources that are only supported in premium SKUs.
This is not enforced on Office 2010 but from a licensing perspective the same restrictions apply.
Can't provide the solution but I can confirm I've been trying this myself this afternoon and I've hit the same problem using a new workbook in Excel 2016. I found a thread elsewhere on the internet where MS had responded to confirm the PQ version in Excel 2016 is slightly older than the version of PQ available as an add-in. Since I can't find any ETA on when the bundled version of PQ in Excel 2016 is due to be updated the next step I was going to try was to see if the add-in version of PQ will install as a temporary measure.
It's might not answer your question, but you could try out Power BI Desktop, which has most of the same Power Query features.

Which Office 365 Plan need to be purchased for creating access web apps

In access 2013, there is an option to create a web app.
My organisation is looking to explore this to way to take existing Access Desktop based application to Web, so that users can remotely also add data and view reports.
From this MS Support link, I came to know that Company will need to purchase office 365 to use Access web app.
When I went to 0ffice 365 business plans there are 3 types. Which one should I purchase? to be able to create web apps.
Our company has domain and website hosted/purchased at GoDaddy. Will we need to change anything on domain? in GoDaddy? If yes, Please specify what or point to post where I can get this info.
What will be other things required to be able to create web apps? Will one user licence sufficient? Will users who use front-end of Web app need to purchase additional licences?
For those with same Question,
Found this post at MS Office Community helpful
That should be any of the Office 365 subscription plans:
SharePoint Online Service Description
After more indepth searching and help from link in above answer,
Office 365 Business Essential did the job.
The web app is completely different than the Desktop, SO will now need to learn fresh.

Upgrading to Access 2010 - what does one need to buy for pro development and distribution?

I use Access 2000 at the moment with a Sagekey Access 2000 MSI Wizard.
For the ability to distribute my app as a runtime I had to buy the Office 2000 Professional software. I then realised for effective and reliable installation I had to buy the Sagekey runtime.
This all works well.
Lately I feel I could benefit from the features of a later version of Access. I can't seem to find info on what I need to buy specifically to put myself in the same position as I am now (shipping MDEs with a Sagekey installer to customers) but using Access 2010 instead.
Can I just buy Access 2010 on it's own these days? I'm checking with Sagekey about support for Access 2010 as it doesn't appear to be listed on their site - Access 2007 is the latest there - but of course Access 2007 seems a bit like an endangered species so I think I should avoid that.
Back in the Access 2000 days, the developer kit and extensions was quite expensive for Access and was a SEPERATE purchase. And as you found out, you still needed to purchase a commercial installer like sagekey. Having to purchase both was quite expensive.
Today, the developer kit and runtime system for Access 2010 is free. However, that system still ships with a very weak install and setup system that tends to cause problems if the end user has other versions of Access installed. So, once again, your best bet is sagekey.
There is a buy now button on their page that shows 2007, but if you click on the order tab a 2010 version is also available.
So at least the runtime is free for Access, and is included for the basic price of Access. This does reduce the cost of this system overall.

Internet synchronization for Access 2000 using Windows Server 2008 and IIS 7.5

I am using Access2000 and Developer Tools, JRO for internet synch, RepMan 4, and was using Win Server 2003 (dedicated server). Just upgraded to Win Server 2008 and have been trying to get Internet synch operational, but with no luck. Here's my problem: I see that MS is urging/forcing subscriptions to SharePoint2010 for internet synchs, however I am not sure that their new platform is as useful to me as their old. Each company I distribute to will run a runtime version of my access application at multiple locations(could be 1 location per company, could be 100). They need to be able to direct synch within each location via LAN (anywhere from 2 to 20 computers). They do not always have an Internet connection (they are at sea), and when they do, it's by satellite and transmission costs are high. And so occasionally they will connect with one computer and perform Internet Replication to send data to home office(could be daily, weekly, or monthly). My current means of synching via JRO is very simple. After attaining an Internet connection, just open a form and either click the synch LAN button or the synch Internet button. Also, by not utilizing automatic synchs, we avoid corrupting other replicas when one is bad or a user has deleted massive amounts of data inadvertently (since deletes always win).
I feel that eventually I will have to update to Access2010 just to keep abreast on new developments in MS (i.e. new .PDF reports instead of .SNP). I recently purchased Office 2010 Pro in order to begin looking into this, but of course this will take some time to work thru.
Here are my questions:
Will SharePoint2010 allow for only one subscription per remote location to handle synchronization back to main office, or would every replica that performs a direct synch at the remote office be required to maintain a Sharepoint2010 subscription?
Can I still use JRO to complete direct synchs among replicas at a remote location and within the home office, and therefore only use Sharepoint 2010 to pass those updates via Internet to the home office.
Will Sharepoint 2010 Enterprise allow me to host multiple company databases in one central account (similar to RepMan4), or must I set up a separate account for each of my customers? If so, do I need to purchase a copy of Sharepoint 2010 for each of these customers?
Will Sharepoint 2010 handle basic data replication and/or design updates in a similar manner to my current set-up? Will I be able to utilize my custom conflict manager?
Also- do you have any info whether Internet synchronizations are indeed capable utilizing Access2000 viaIIS 7.5 on Windows Server 2008 with RepMan4? I have not found anyone who has accomplished this – latest suggestion is that maybe IIS needs to be run in a 32-bit environment in order to open the synchronizer, but I have not yet tried this.
My company makes a product called [EQL OnWeb - link deleted] which is designed for exactly your use case. It works with getting Access 2000 databases on the web without rewriting them first, and there's a free trial so you can see if you like it.
I won't comment in detail on SharePoint 2010 because clearly I'm biased... but I like our product better :)