Dealing with the Access 2003 255 field limit on tables.

Quite often I've had the misfortune of having to create Access applications. If you're reading this then you understand the problem with the 255 field limit. The best way I've found to combat this is to create a view in Excel using the External Data tool, then turn the query I use for that into an OLAP cube, then set the cube to auto-refresh when opened. The problem is that you're limited to 65,536 rows of data, so you may have to make several of these.

No Current Record in Microsoft (MS) Access Query

I just battled this for two days before finding an answer so I want to post it. I recently was getting a "No Current Record" error in my MS Access query when I tried to include a Yes/No field and use a left join.

I finally figured out why: Access forces the field to be 0 or -1 (in my case) and does not allow nulls. When you have a left join you can get nulls. The solution was to convert the Y/N to text and then do the comparison.

In your Query, just build it like this:

ucase([Y/N Field Name])

this makes it a nullable text field instead of a Y/N.

Good luck!

Too hillariously awesome.

I'm tired of Sarah Palin's "Let's pretend that American's want the dumbest person in office" approach. Tired of her making intelligence seem unnecessary. I personally WANT the Harvard big-wig in office. I want the SMARTEST PERSON IN THE COUNTRY to run the country. Look, we've had an idiot in office for 8 years and we're now in the worse shape of our past two generations.

Sarah Palin needs to drop the "I'm the right person because I'm a typical person" campaign. We're in a crisis and we need intelligence, not home-spun tales from the soccer field.

 

This is my first HDR picture taken using my Canon XSi DSLR. I did the HDR work in qtpfsgui and touched it up using The GiMP.

This kid is too damned cute