I have a database that has been in use for many years. It was upgraded to .accdb back in 2010. It is currently being accessed using Access for Office 365 on a Windows 10 Pro computer. The database is stored on a network drive.
Everything has been working fine until today. Today I'm getting an error that the query [query name] is corrupt. I created a new query that does the same thing as the old one and am getting the same error message on the new query. I've added the database location to the trusted location, but that hasn't fixed the error.
The query in question is a simple update query.
It looks at one value in one table.
Sets it to 0 if the current value is null.
Any ideas where I should look next?
Thank you for any and all help.
Related
I'm wondering if anyone having the same issue.
I have an ASP.NET MVC 5 web application that create Purchase Orders and insert them in SQL database.
It has been working on all browsers(including Chrome) for years but lately it has been intermittently duplicating the insert record in SQL database whenever SaveChanges() is called only in Chrome(Safari/Edge are working properly).
I tried to check if the record exist in the database before the savechanges() is called but i guess it's duplicating the record the second savechanges() is called the first time.
Anybody else is experiencing this issue with Chrome?
I have logged this on the Chrome Forum as well as it feels like a bug in Chrome browser!!!!
Thanks in advance
One of my clients is using Quickbooks 2018 desktop pro and we have recently upgraded them from 2016. When trying to run a report, we are getting a different balance than what is recorded. We then try to Verify through the utilities and we get an error that states, "One of your employees SSN is invalid" "One of your employees DOB is invalid" then it crashes the program. Trying to edit this specific employees info also triggers the errors/crashes the program. I have also tried to export the employee list but errors trigger again seemingly at each outlet I try. Any suggestions?
Sounds like two different ( and unrelated issues)
You can try this...
1) Correct the employee issues: Go back to your original 2016 file -- hopefully you can restore it from a backup made prior to the upgrade -- and edit/correct the employees there, then update the file again. Just to verify, try editing the employee again in the updated file... if still an issue, either the original or the update may be (getting) corrupted during the upgrade, in which case you'll likely need to talk to Intuit's tech support.
2) Balance issues: make sure your comparing the reports with the same 'basis' method, Accrual or Cash, shouldn't matter, but they both must be the same basis.
Good Luck.
Since monday my Android app users have been getting a 500 return code from Fusion Tables whenever they try to save their data.
Within the app we convert all their geo data into csv format and POST it to Fusion Tables using an insert command. Before Sunday this appears to have been working fine. Starting on monday we are seeing problems like the the following logcat with 100% of our saves:
10-29 12:18:34.083: W/System.err(3650): java.io.FileNotFoundException: https://www.googleapis.com/upload/fusiontables/v1/tables/[valid table ID redacted]/import?access_token=[valid access token redacted]
Despite the error message, manually checking the Fusion Tables shows no error and all seems fine.
Given the other problems with Drive on monday I'm guessing that the team rolled out some changes over the weekend. Perhaps there was a change that means I need to terminate the stream with a special character or something. Anyone else experiencing a similar problem or have any idea what is going on?
I'm up to about 30 complaints from users now and it's getting a bit old.
We believe this is resolved now -- are you still getting the reports? If it's the problem we identified, the imports were in fact eventually completing even though an error status was returned.
Good morning: I've recently moved offices and I was assigned a new userID and profile. My dilemma is that when logging into SSMS the stored procedures I've created under my old userID are no longer in the list.
How/where would I be able to retrieve those? I'll need to have server admins allow me access to my old login, if that's what I need to do? And then how do I bring them over to my new userID?
I meant to add that I first noticed this when I went to call a stored procedure from when refreshing a data table in Excel and it spit out an error.
Thanks in advance for all the suggestions/ input!
Robin
the server admins got back to me, and it was a matter of updating my permissions and creating a new login with dbo on the database with my new userID and ADLogon. After they performed that change, I was able to see all objects and run commands. Life is good!
On my development machine everything is working fine, however as soon as I publish it to the server I get
System.InvalidCastException: Specified cast is not valid
This is happening on
db.SubmitChanges();
I've check out https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=351358 and it still causes me errors
I also ran the Windows Update and everything is up to date on the server
You don't say what you're trying to submit to the database, so anything I suggest will be (educated) guesswork. However, the thing that springs to mind is to check is the date format on your machine vs the server. This could be at the OS level or the database level.
If your machine is UK and the server is US then if you had a string representing the date in UK format (e.g. 30/9/2009) it would fail as there aren't 30 months.
However, as you say it's not this specific problem, look for differences between your development environment and the server to highlight what could be the problem areas.
An incomplete list of things to check:
different operating systems. I'm assuming you're on XP/Vista and the Server is on Windows Server. Get a machine with the same OS and debug it there. Is your development machine 32 bit and the server 64 bit (or vice versa)?
different versions of the .NET runtime. Make sure that the server is running the same version as your development machine.
other libraries etc. Is there something installed on your development machine you've not installed on the server?
Okay I have resolved the issue.
What appears to be the problem is that I have tables that have Id as Int and the Primary keys and also have GUID's as a fields which is defined as Unique, and the Guid field is a key to another table and being used as a foreign key.
When I set the Guid field as the primary key in the table the problem goes away.
I've not created a test project to prove this, due to time constraints as we are going live next week
Have you changed the data type of any column in the model, or in the database? That exception is usually thrown as a result of a mismatch between the data type used in the L2S model and the data type used in the database.
Alternatively, do you have any varchar(1) or nvarchar(1) fields? If so, the L2S designer will by default map those to System.Char. This is an incorrect mapping since a varchar(1) or nvarchar(1) can contain an empty string while a System.Char must contain exactly one character, and can result in InvalidCastExceptions being thrown (although that mismatch usually occur when retrieving data, not when submitting)...
I had this problem too. I had changed into my local database, and forgot to make this changes to my production database.
I face the same exception when calling:
DataContext.SubmitChanges();
after altering an object on the context. and same it worked in development machine and in the server, i got same cast error.
I had an association between two tables using a string property as the key.
To fix, I removed the association.