Recent content by keith_pyrasoft

Still unresolved I still encounter this problem... I recently experienced it on a PC that had not been displaying it and now is - I currently suspect some sort of windows update. Anyone else getting this effect?

As a further thought - Does anyone out there know of a link between User-defined types and UTILITY.MDA?

I recently overcame mde build problems that I had been encountering (separate post) by realising that the Access 97 db in question had inappropriate references in it (namely Microsoft DAO 2.5/3.5 Compatibility Library and UTILITY.MDA instead of Microsoft DAO 3.51 Object Library). This I...

I finally got to the bottom of this one.... It was a self-inflicted problem, in a sense. The db affected was my oldest application, and contained references to Microsoft DAO 2.5/3.5 Compatibility Library and utility.mda. When I replaced these with Microsoft DAO 3.51 Object Library, my mde...

Thanks for that one Mile-O-Phile .... I hadn't thought of that. I always try to be tidy when deleting objects, but it is very easy to leave code behind. I shall start to look for orphaned code...... it's not going to be easy though! And I'm still baffled by the sometimes will compile /...

Further attempts I have made are: Decompiling, which seemed to me not to work properly on this database, because it gave an error on the first attempt, and then on a second try merely reported that it had converted Utility.mda, with no evident improvement or size reduction to my mdb. I have...

Hi Rich Yes, the code is compiled and saved. I have the problem with only one mdb/mde, which happens to be my largest application.

I have a strange situation with an access 97 database. When building an mde file, it will sometimes give an error, and sometimes not. The error is 'Can't open database (blah). It may not be a database that your application recognises, or the file may be corrupt.' I have been chasing this one...

In case it throws any more light on the matter: On one of my applications I have removed Limit to List from one of the misbehaving combos, and this alleviates the problem as it allows a valid entry to be typed in. However, the underlying problem is still there, because auto expand doesn't...

OK Try changing the name of the field to something else than 'Date'.

I may be way off the mark on what is going on here, but it brings back the horrific problems i was experiencing recently. Might be worth checking them out: http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=50355

Sorry - I should have been clearer. In Form properties, click the On Open property and use the Code Builder to give you the Private Sub Form_Open(Cancel As Integer) End Sub routine. Insert the statement Me!MyField = Date where MyField is the name of your date text box on...

OK. Remove those assignments from the Default Value properties, and instead set the values against the Open property of the form (or the Current property, depending on how you want it to work). eg: Private Sub Form_Open(Cancel As Integer) Me!CostDate = Date End Sub This should provide...

vivian My occurrence of this problem was in a form I designed when I first started using Access, and was experimenting with techniques. I found that I had assigned =date() and =time() to the Default Value properties of the fields concerned so that they were automatically loaded for data entry...

frustration..... I'm still no nearer to solving this one........ is it just not happening to anyone out there??