Search results

  1. I

    Microsoft .NET Blazor

    George the cost is for the entire app... you can have as many users as you want. The more users and more complexity the more server power you need to buy. You are just paying for server power which you can adjust as needed. There is no licensing involved at all with Azure and the Blazor /...
  2. I

    Microsoft .NET Blazor

    The $100 is for a single application and includes the Web Server, SQL Server and the SSL Certificate. You control the costs in Azure by choosing the power of the Servers you would like. I buy the Domain Names on GoDaddy. For simple CRUD apps I am paying ~$18.25 USD / month and this includes...
  3. I

    Microsoft .NET Blazor

    MudBlazor's free UI library is the key to all this. The community is open source and very friendly. https://mudblazor.com/docs/overview https://themes.arctechonline.tech/
  4. I

    Microsoft .NET Blazor

    The only cost is hosting on Azure. Visual Studio and all the Libraries are free. For around $20 / month you can support a small Web App with CRUD and basic querying. I typically spend around $100 - $150 / month for better performance. Deployment to Azure is simply clicking the deploy button...
  5. I

    Microsoft .NET Blazor

    Yes. I use it with SQL Server on Azure. I have migrated our reporting product to Microsoft Blazor and the results are fantastic. I have also built a small project that has CRUD also hosted on Azure with SQL Server.
  6. I

    Microsoft .NET Blazor

    I have been migrating my MS Access applications to Microsoft's latest .NET technology called Blazor. In combination with the MudBlazor open source library I have been able to create excellent results. I find developing in Visual Studio / .NET / Blazor / MudBlazor very rapid and this is the...
  7. I

    Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. (System.Data)

    I don't import Excel directly into SQL Server anymore. I first import into MS Access, cleanup the data in MS Access and then import into SQL Server using the Migration Assistant. The Migration Assistant creates the indexes and the timestamp field for me. This appears to be the best approach...
  8. I

    Cannot Link to SQL Server Table that contains the Float Data Type

    OK, I'll stick with Decimal(9,6). Thank you everyone.
  9. I

    Cannot Link to SQL Server Table that contains the Float Data Type

    Hello Access World, I am storing Lat / Long from GoogleMaps API in SQL Server. It is recommended to use the Float Datatype to store Lat / Long, however, when I use Float MS Access presents me with the following error when I open the Linked Table. When I store Lat / Long as Decimal(9,6)...
  10. I

    SQL Server importing strange characters despite specifying nvarchar

    Understood. Thanks everyone.
  11. I

    SQL Server importing strange characters despite specifying nvarchar

    Thanks Isaac. The Import Flat File was recommended by this SQL Server teacher on YouTube(URL below), who has courses on Udemy. He advises to use the Flat File Import for .csv files. He does cover the Import Data wizard for Excel files later on in the video. Import Tutorial
  12. I

    SQL Server importing strange characters despite specifying nvarchar

    Thank you Tom. I assumed it was Unicode due to the Accent on the e and SQL Server not being able to import it using the Flat File import Wizard. I see now that the e with an accent is still part of the ANSI character set. Yes, MS Access link can process the file correctly and I used SSMA to...
  13. I

    SQL Server importing strange characters despite specifying nvarchar

    The file contains accents in the Province Field as shown in the first post. Waste Class is a field that does not contain any special characters but is longer than 255 so that is probably the truncate message. I was in a rush Sonic so I just decided to go the route that is slower but worked...
  14. I

    SQL Server importing strange characters despite specifying nvarchar

    Thank you Isaac. The codepage feature is available in the Import Data Wizard. Unfortunately, it's not available in the Import Flat File Wizard which is much simpler. That being said I am getting an error using the Import Data Wizard. I decided to import into MS Access and then use the SQL...
  15. I

    Encountered strange interaction between Excel data and MS Access Link / Import

    Exactly, that is what makes this puzzling. I consider this to be a bug. Note, it only starts to falter when you increase the number of Numerical Digits.
  16. I

    Encountered strange interaction between Excel data and MS Access Link / Import

    Thank you George. We actually met in PADU back in the day.
  17. I

    Encountered strange interaction between Excel data and MS Access Link / Import

    Thank you MarkK and George for your feedback. I was able to figure out the cause. When the Field Format in Excel is General the MS Access Link Truncates the 2nd Decimal Digit. When the Field Format is Number with 2 decimals the MS Access Link to the Excel file shows the 2nd Decimal Digit...
  18. I

    Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. (System.Data)

    Hello Access Forum, I am unable to import Excel into my SQL Server due to the error 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. (System.Data) 1) By running EXEC sp_enum_oledb_providers I can see I have Microsoft.ACE.OLEDB.12.0. on my machine. 2) It's...
  19. I

    SQL Server importing strange characters despite specifying nvarchar

    Hello Access Forum, I imported a .csv that contains special Unicode characters using the Import Flat File wizard from SSMS. The .csv shows the Unicode characters properly but the output of the import in SQL Server does not. Please see the below screenshots. I have attached a sample .csv...
  20. I

    Encountered strange interaction between Excel data and MS Access Link / Import

    I believe the issue is with my Excel. The Excel Link doesn't show the 2nd digit and that is where I think he problem originates. When I imported using SQL Server as a .CSV the 2nd digit appears
Back
Top Bottom