Search results

EUREKA! This is what I was looking for, THANKS!! Since this is the first time I've seen this screen, could I ask a few questions? (Please keep in mind, I didn't create this Db and don't purport to be any type of expert on Access). This layout doesn't look particularly intuitive to me. I have...

I think so. Here's a screenshot of the exact message.

Indexed is marked 'No'

Ooookay. So, I'm kind of at a loss here. I have narrowed down my issue to some validation rule or something, but I cannot see any rule in place at all. Here's what happens. Procedurally, I'm trying to duplicate a record on a table. Every time I try, I get a 'duplicate record' error, even...

The database is split into back-end and front-end. The feature request from the users was specifically that they want to have the ability to back up and restore using XML files. The users have no need to merge data; each person is going to have their own records. I can't get into much detail...

I appreciate all the help from everybody here! I was able to progress further on this feature, thankfully. As stated before, I am using individual XML files for each of the tables. Not ideal, but it is what it is. The export works great, otherwise. Now, for the import. I'm having some issues...

No worries, I'd be happy to clarify! RE: ExportXML; right now I have exported each table to a separate XML. This is less than ideal, but I'll take it. RE: ImportXML; the issue is circular dependencies. I have something like 110 tables, and the relationships between them are...well it's like...

Each user needs a stand-alone back end. Again, I'm all ears and open to a better solution if you have one. The users specifically asked for XML for future compatibility, but if an argument can be made for another format...

Yes, I began with questions about ExportXML, you're right, but ImportXML is its counterpart -- they go hand in hand. ExportXML won't do me any good if ImportXML can't work. I can give broad strokes about why I want to do this, yes. The idea is this: I'll have different instances of this same...

Yeah, that's the entire issue. That, and relationship dependencies when importing. I just want a simple export/import capability... Is there something I'm missing in the ImportXML method? Is there a way to import all the data simultaneously so I don't get dependency complaints?

I would like one XML file to have all my tables exported into. So... <dataroot ...> <tbl1> <tbl1 data...></tbl1 data...> </tbl1> <tbl2> <tbl2 data...></tbl2 data...> </tbl2> ...

Okay, I know how to export specific tables to XML using Application.ExportXML and I was able to successfully use that. But it doesn't quite fit what I need... I'm looking to export ALL tables to XML, and there are many. Many relationships, too. I just want to export the data from each table...