Just moved a database app over to another server, along with the associated web pages. There's also a little VB app that updates the database. Why they didn't do that in the web pages, I don't know. Something to do with having to update the mainframe, and the database at the same time. No idea what's going on there.
Anyway, the switch went fine, and people could read everything, but for some reason, the DB app (not the web one) is now trying to insert Null values where Nulls aren't allowed. Weird. I don't think it was doing this before, so it must have something to do with the DB at the server.
Anyone have any ideas why an app would all of a sudden want to start throwing nulls?
2 comments:
I have the answer. The database was supposed to populate that field itself with a (getdate()), but that didn't come over in the copy. Same for several other fields. Recopied the DB with the added options, and there you go. In like Flynn. Or something like that.
Glad you figured it out Sammich.
Post a Comment