Search results

may have an idea: I talked to the SQL administrator who controls the back end. When I asked her to add default values for 2 fields yesterday, she said one of them formerly accepted NULL values in for a field that was included in a union query...so maybe the Form display wasn't happy about the...

Before I got a chance to change anything code-wise, the records showed up this morning like they'd never been away. I've no explanation...perhaps some delay in the requery instruction at the SQL server? I really have no idea. If I learn any more, I'll post. Lisa

I never thought to do that I'll try that. Lisa

This is with a database that I'm currently testing against LINKED tables in a SQL back end. I wrote a VBA Import process which appears to work: records from import table are added to ticketorder and ticketorderdetail tables as expected with data in the correct locations, and the data shows up...

I now understand that it requires entry of the master table information (order) first, then adding the detail level records (orderdetail) after. My thanks for the assistance.

Feels like there you should be a way to write a nested loop that handles this, but I'm not familiar enough with the SQL language part of it to be certain. Worst case I could always take 2 full swipes at the data: first insert the order, then take another run through the to pick up the...

I have an existing database being used for for order processing (normalized, working). The order table houses the general order info and a separate detail table holds 1 or more orderdetail records for each order in the order table, related by orderID. A user has asked that I find a way to...

Holy cow! I forgot to even check that. My thanks. LIsa

Testing on a split database, SQL back end, Access 2007 front. I haven't priviledges on SQL so I had that group add a new field to a table. They did it, and I refreshed the tables - so I can "see" the new field in Access land. When I try and add the new field to the form in Design Mode, the...

I've been cluging together Access Databases for several years, but primarily for my own use. Then people at work learned I did it and suddenly my smacked together database became the workhorse for our group. It wasn't really designed as a multi-user system...and suddenly it's becoming a...