Transitioning From Access To Web Sites
I have a question for the individuals out there that are moving to a web interface from Access What it the best app/program to use to make the move from using Access to using web pages? I've been tasked with converting the Access app that I have been working with for years to make it a web "site", which would be converting the entire application - forms, reports, etc. so that it can be used via web browser instead of MS Access. I am in no means a website developer, but I'm always open to learning new things. Mind you, one of the databases has in excess of 12K lines of VBA. I want to be able to use some of the same techniques as what I've done with VBA and to be able to create a good user experience on the front end plus create some additional enhancements. Al of my searches have not yielded anything helpful. Thanks in advance. Jeff
Sharepoint Linked Table - Help
Hi, I have an older sharepoint list that collects concrete deliveries to site (Insitu Concrete), i have a new Sharepoint list that that shows the price for each mix type (Concrete_Mix_Design_Costs). I cannot run a query or use DLookup succesfully to add the price to each delivery. Above are the tables i want to put the price against each delivery based on Mix Type. Any help would be much appreciated, I am a builder not a computer person but have muddled my way to building a database that runs our procurement etc, but despite hours of effort i am going nowhere with this. Thanks
MS Access Handling Nulls In Query Formula
Hi all, I have this formula in Access: IIf([Init_Static_P] < 0 And (Nz([Adj_Static_P], -9999) < 0), "Resolved", "Not resolved" which keeps outputting an #Error when Adj_Static_P is null which will happen. I need the nulls in my dataset. Whenever Init_Static_P is < 0 and or Adj_Static_P is < 0, it works as it should outputting "Resolved" and vicer versa, however it does not work whenever there is any instance of Adj_Static_P as a blank value. Does anyone know how I can handle the nulls so that if the Init_Static_P is >0 and Adj_Static_P is null, then it would output "Unresolved", and if Init_Static_P is <0 and Adj_Static_P is null then it would output "Resolved" instead of #Error? Output should be as follows: Init_Static_P Adj_Static_P Result >0 Null "Not resolved" >0 >0 "Not resolved" <0 Null "Resolved" <0 < 0 "Resolved" Thanks in advance! <3ODBC --call failed. [Sage][Support] (40190) Data conversion algorithm not supported for...
ODBC --call failed. [Sage][Support] (40190) Data conversion algorithm not supported for SQL_BIT to SQL_TYPE_DATE. (#40190) I'm trying to execute an update statement in MS Access using the following, but keep getting an error message: Any ideas what I'm doing wrong here? Appreciate any feedback.Fallas AUTHENTICATOR
Tengo un problema enorme y es que no puedo iniciar sesión en mi cuenta de Outlook la cual tengo relacionada a Authenticator, me dice que me va a llegar un código y nunca me llega doy para ingresar el código manual y al ingresar el que me arroja en la app me dice que el código es erróneo, y no puedo montar un ticket porque para ello necesitaría iniciar sesión en la cuenta, y hablando con los soportes de chat no me dan una solución, soy de Colombia alguien me puede ayudar.
Has Microsoft forsaken Access? (by an "amatuer" Access developer)
It seems to me that, over the past eight years or so, Microsoft has increasingly underestimated and misinterpreted the benefit of Access. For example, I can't understand why MS would develop an application like Forms without creating the functionality that would allow for the easy export of data collected in a form to an Access database application. For me, the Forms app is useless if I cannot easily figure out how to dump the data I collect using Forms into my Access database application. For the record, I am not an Access developer. I am merely a lawyer who lacks proficiency in any programming language but understands the concept and benefits of relational databases. My understanding was forced to evolve over the past twenty years as a result of my numerous needs to collect, mine, and utilize clean data in the most efficient manner available that also integrated into daily operations and, thus, minimized the creation of additional data-entry tasks that would inevitably be ignored whenever things got busy. In most cases, the "amateur" applications I created to collect and mine critical data -- originally intended as an interim solution -- became the "permanent" solution after I left the particular project. Not surprisingly, this happened because other colleagues were not able to sufficiently communicate their detailed needs in a format that professional application developers could understand. Over twenty years have passed since I began working with Access, and yet, based on my observations, this vast communication gap between the end user and the application developer continues to be a significant barrier to progress. This is remarkable in light of the fact that the costs of the hardware/software required to realize greater efficiency have reduced dramatically over the same period. I have often explored other options for creating and maintaining a relational database application tailored to my specific needs, but Access remains the easiest and most cost-effective option -- especially when my needs demand more complex functionality. My experiments with pre-packaged applications have always led to the same conclusion: Access enables me to design an app in far less time that does more at a lower cost and that can be more easily adopted by other end users in my office. I have often explained it to both developers and end users in this way: Access enables me to compose complex musical pieces to be performed by a small orchestra without first having to learn to read music. Unfortunately, it appears to me that MS fails to appreciate the significant benefit this attribute could provide to countless new users. Another under-valued benefit that only Access can provide to smaller organizations: when end users learn to create simpler database applications in Access, their ability to communicate complex functionality needs to professional application development teams simultaneously and exponentially improves. This, in turn, reduces unexpected costs, frustrations, and disappointed expectations that too often result from ineffective communication between the end users and the development team: an all-too-frequent experience that leads to long-term negative consequences of increased costs associated with end-user training and adoption; increased resistance to change and innovation; reluctance among leaders of smaller organizations to pursue further development projects. For the foregoing reasons, I urge MS to re-evaluate the significant needs that could be fulfilled by promoting Access as a cost-effective tool for small businesses, organizations, and innovative grant-funded projects all of which typically lack both the financial resources to hire a professional developer and the time/capability required to communicate needs during the development process. I also hope that MS will pursue functionality that allows amateur developers/end users like me to easily integrate data collection from newer applications like Forms with the storage and querying functionality provided by an Access database application. To promote Access for use in smaller organizations, MS should, in my opinion, design training materials and experiences for beginners that present design and functionality concepts in a manner that is tailored to the varying perspectives of different categories of end users. For example, paralegals and attorneys working in a small law office would immediately grasp the benefit of a system that eliminates the need to repeatedly type the same information into multiple documents throughout their workday. As such, I suspect a training class that took these users through the process of creating an Access database app and integrating the app with Word to allow for the export/merging of field data to multiple legal document templates would both be well received and ignite a desire to pursue other projects.
